From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH 1/1] io_uring: sanitise ring params earlier
Date: Fri, 31 Jan 2025 16:56:53 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <363ba90b83ff78eefdc88b60e1b2c4a39d182247.1738344646.git.asml.silence@gmail.com>
On Fri, 31 Jan 2025 17:31:03 +0000, Pavel Begunkov wrote:
> Do all struct io_uring_params validation early on before allocating the
> context. That makes initialisation easier, especially by having fewer
> places where we need to care about partial de-initialisation.
>
>
Applied, thanks!
[1/1] io_uring: sanitise ring params earlier
commit: aee81931e48b5d236600affba2e7a2a2dd2ac639
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-01-31 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 17:31 [PATCH 1/1] io_uring: sanitise ring params earlier Pavel Begunkov
2025-01-31 23:56 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173836781320.549578.4470486333015276206.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox