From: Tudor Cretu <tudor.cretu@arm.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Cc: asml.silence@gmail.com, kevin.brodsky@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring/kbuf: Fix size for shared buffer ring
Date: Fri, 28 Apr 2023 11:29:40 +0100 [thread overview]
Message-ID: <002c3a2a-df57-1997-1739-9675a6c8dd46@arm.com> (raw)
In-Reply-To: <03b13c8f-0f4c-0692-b2f0-e90d7877e327@kernel.dk>
On 27-04-2023 19:42, Jens Axboe wrote:
> On 4/27/23 8:31 AM, Tudor Cretu wrote:
>> The size of the ring is the product of ring_entries and the size of
>> struct io_uring_buf. Using struct_size is equivalent to
>> (ring_entries + 1) * sizeof(struct io_uring_buf)
>> and generates an off-by-one error. Fix it by using size_mul directly.
>>
>> Signed-off-by: Tudor Cretu <tudor.cretu@arm.com>
>> ---
>> io_uring/kbuf.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
>> index 4a6401080c1f..9770757c89a0 100644
>> --- a/io_uring/kbuf.c
>> +++ b/io_uring/kbuf.c
>> @@ -505,7 +505,7 @@ int io_register_pbuf_ring(struct io_ring_ctx *ctx, void __user *arg)
>> }
>>
>> pages = io_pin_pages(reg.ring_addr,
>> - struct_size(br, bufs, reg.ring_entries),
>> + size_mul(sizeof(struct io_uring_buf), reg.ring_entries),
>> &nr_pages);
>> if (IS_ERR(pages)) {
>> kfree(free_bl);
>
> Looking into this again, and some bells ringing in the back of my head,
> we do have:
>
> commit 48ba08374e779421ca34bd14b4834aae19fc3e6a
> Author: Wojciech Lukowicz <wlukowicz01@gmail.com>
> Date: Sat Feb 18 18:41:41 2023 +0000
>
> io_uring: fix size calculation when registering buf ring
>
> which should have fixed that issue. What kernel version are you looking at?
Hi Jens,
Thank you for your message. Indeed I was looking at a slightly older
version of the kernel. Apologies for the noise!
Kind regards,
Tudor
>
prev parent reply other threads:[~2023-04-28 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 14:31 Tudor Cretu
2023-04-27 14:35 ` Jens Axboe
2023-04-27 18:42 ` Jens Axboe
2023-04-28 10:29 ` Tudor Cretu [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=002c3a2a-df57-1997-1739-9675a6c8dd46@arm.com \
--to=tudor.cretu@arm.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®