All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [PATCH v2] io_uring: reg buffer overflow checks hardening
Date: Thu, 25 Mar 2021 19:15:04 +0000	[thread overview]
Message-ID: <813d0f09-3842-b224-47d6-5c1da5a28537@gmail.com> (raw)
In-Reply-To: <e8d423fa-5b0d-a337-e921-00697d24028f@kernel.dk>

On 25/03/2021 19:17, Jens Axboe wrote:
> 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.

right, thanks!

-- 
Pavel Begunkov

      reply	other threads:[~2021-03-25 19:20 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
2021-03-25 19:15   ` Pavel Begunkov [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=813d0f09-3842-b224-47d6-5c1da5a28537@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.