From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH v2] io_uring: reg buffer overflow checks hardening
Date: Thu, 25 Mar 2021 13:17:25 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <2b0625551be3d97b80a5fd21c8cd79dc1c91f0b5.1616624589.git.asml.silence@gmail.com>
On 3/24/21 4:59 PM, Pavel Begunkov wrote:
> We are safe with overflows in io_sqe_buffer_register() because it will
> just yield alloc failure, but it's nicer to check explicitly.
>
> v2: replace u64 with ulong to handle 32 bit and match
> io_sqe_buffer_register() math. (Jens)
Applied for 5.13 - btw, and I think that was an oversight on this one,
just put the version stuff below the '---' as it should not go into
the git log.
--
Jens Axboe
next prev parent reply other threads:[~2021-03-25 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 22:59 [PATCH v2] io_uring: reg buffer overflow checks hardening Pavel Begunkov
2021-03-25 19:17 ` Jens Axboe [this message]
2021-03-25 19:15 ` Pavel Begunkov
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 \
[email protected] \
[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