From: Jens Axboe <axboe@kernel.dk>
To: Qingyue Zhang <chunzhennn@qq.com>
Cc: aftern00n@qq.com, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] io_uring/kbuf: fix infinite loop in io_kbuf_inc_commit()
Date: Wed, 27 Aug 2025 20:50:24 -0600 [thread overview]
Message-ID: <8ed15a17-618f-4277-afc3-934939292060@kernel.dk> (raw)
In-Reply-To: <tencent_87B68C160DC3F4AE06BD6DF0349B1B235E05@qq.com>
On 8/27/25 8:49 PM, Qingyue Zhang wrote:
> On Wed, 27 Aug 2025 20:08:05 -0600, Jens Axboe wrote:
>> I don't think there's anything wrong with the looping and stopping at
>> the other end is of course a safe guard, but couldn't we just abort the
>> loop if we see a 0 sized buffer? At that point we know the buffer is
>> invalid, or the kernel is buggy, and it'd be saner to stop at that
>> point. Something ala:
>>
>>
>> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
>> index 394037d3f2f6..19a8bde5e1e1 100644
>> --- a/io_uring/kbuf.c
>> +++ b/io_uring/kbuf.c
>> @@ -42,7 +42,8 @@ static bool io_kbuf_inc_commit(struct io_buffer_list *bl, int len)
>> buf_len = READ_ONCE(buf->len);
>> this_len = min_t(u32, len, buf_len);
>> buf_len -= this_len;
>> - if (buf_len) {
>> + /* Stop looping for invalid buffer length of 0 */
>> + if (buf_len || !this_len) {
>> buf->addr += this_len;
>> buf->len = buf_len;
>> return false;
>
> Good idea, it looks nice to me.
I'll send it out, I amended the commit message a bit too.
--
Jens Axboe
next prev parent reply other threads:[~2025-08-28 2:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250827114339.367080-1-chunzhennn@qq.com>
2025-08-27 11:44 ` [PATCH 2/2] io_uring/kbuf: fix infinite loop in io_kbuf_inc_commit() Qingyue Zhang
2025-08-27 14:30 ` Jens Axboe
2025-08-27 21:45 ` Jens Axboe
2025-08-27 21:59 ` Keith Busch
2025-08-27 22:23 ` Jens Axboe
2025-08-28 1:36 ` Qingyue Zhang
2025-08-28 2:08 ` Jens Axboe
2025-08-28 2:49 ` Qingyue Zhang
2025-08-28 2:50 ` Jens Axboe [this message]
2025-08-28 2:58 ` Jens Axboe
2025-08-28 3:27 ` Qingyue Zhang
2025-08-28 11:50 ` Jens Axboe
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=8ed15a17-618f-4277-afc3-934939292060@kernel.dk \
--to=axboe@kernel.dk \
--cc=aftern00n@qq.com \
--cc=chunzhennn@qq.com \
--cc=io-uring@vger.kernel.org \
--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