From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, Martin Michaelis <code@mgjm.de>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/2] io_uring/kbuf: support min length left for incremental buffers
Date: Tue, 28 Apr 2026 13:53:10 -0400 [thread overview]
Message-ID: <87ik9bj7jt.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <20260428154557.2150818-3-axboe@kernel.dk> (Jens Axboe's message of "Tue, 28 Apr 2026 09:44:50 -0600")
Jens Axboe <axboe@kernel.dk> writes:
> From: Martin Michaelis <code@mgjm.de>
>
> Incrementally consumed buffer rings are generally fully consumed, but
> it's quite possible that the application has a minimum size it needs to
> meet to avoid truncation. Currently that minimum limit is 1 byte, but
> this should be a setting that is the hands of the application. For
> recvmsg multishot, a prime use case for incrementally consumed buffers,
> the application may get spurious -EFAULT returned at the end of an
> incrementally consumed buffer, as less space is available than the
> headers need.
>
> Grab a u32 field in struct io_uring_buf_reg, which the application can
> use to inform the kernel of the minimum size that should be available
> in an incrementally consumed buffer. If less than that is available,
> the current buffer is fully processed and the next one will be picked.
>
> Cc: stable@vger.kernel.org
> Fixes: ae98dbf43d75 ("io_uring/kbuf: add support for incremental buffer consumption")
> Link: https://github.com/axboe/liburing/issues/1433
> Signed-off-by: Martin Michaelis <code@mgjm.de>
> [axboe: write commit message, change io_buffer_list member name]
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
> ---
> include/uapi/linux/io_uring.h | 3 ++-
> io_uring/kbuf.c | 8 +++++++-
> io_uring/kbuf.h | 7 +++++++
> 3 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h
> index 17ac1b785440..909fb7aea638 100644
> --- a/include/uapi/linux/io_uring.h
> +++ b/include/uapi/linux/io_uring.h
> @@ -905,7 +905,8 @@ struct io_uring_buf_reg {
> __u32 ring_entries;
> __u16 bgid;
> __u16 flags;
> - __u64 resv[3];
> + __u32 min_left;
> + __u32 resv[5];
Honest question, isn't this a property of the specific operation and/or
fd being operated, instead of the buffer_reg?
> };
>
> /* argument for IORING_REGISTER_PBUF_STATUS */
> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
> index 43e4f8615fe8..63061aa1cab9 100644
> --- a/io_uring/kbuf.c
> +++ b/io_uring/kbuf.c
> @@ -47,7 +47,7 @@ static bool io_kbuf_inc_commit(struct io_buffer_list *bl, int len)
> this_len = min_t(u32, len, buf_len);
> buf_len -= this_len;
> /* Stop looping for invalid buffer length of 0 */
> - if (buf_len || !this_len) {
> + if (buf_len > bl->min_left_sub_one || !this_len) {
Cosmetic, but perhaps store min_left_sub_one instead of min_left itself? the
buf_len must be >= min_left, and that is easier to read. (buf_len &&
buf_len >= min_left || !this_len)
> WRITE_ONCE(buf->addr, READ_ONCE(buf->addr) + this_len);
> WRITE_ONCE(buf->len, buf_len);
> return false;
> @@ -637,6 +637,10 @@ int io_register_pbuf_ring(struct io_ring_ctx *ctx, void __user *arg)
> if (reg.ring_entries >= 65536)
> return -EINVAL;
>
> + /* minimum left byte count is a property of incremental buffers */
> + if (!(reg.flags & IOU_PBUF_RING_INC) && reg.min_left)
> + return -EINVAL;
> +
> bl = io_buffer_get_list(ctx, reg.bgid);
> if (bl) {
> /* if mapped buffer ring OR classic exists, don't allow */
> @@ -683,6 +687,8 @@ int io_register_pbuf_ring(struct io_ring_ctx *ctx, void __user *arg)
> bl->mask = reg.ring_entries - 1;
> bl->flags |= IOBL_BUF_RING;
> bl->buf_ring = br;
> + if (reg.min_left)
> + bl->min_left_sub_one = reg.min_left - 1;
> if (reg.flags & IOU_PBUF_RING_INC)
> bl->flags |= IOBL_INC;
> ret = io_buffer_add_list(ctx, bl, reg.bgid);
> diff --git a/io_uring/kbuf.h b/io_uring/kbuf.h
> index abf7052b556e..401773e1ef80 100644
> --- a/io_uring/kbuf.h
> +++ b/io_uring/kbuf.h
> @@ -32,6 +32,13 @@ struct io_buffer_list {
>
> __u16 flags;
>
> + /*
> + * minimum required amount to be left to reuse an incrementally
> + * consumed buffer. If less than this is left at consumption time,
> + * buffer is done and head is incremented to the next buffer.
> + */
> + __u32 min_left_sub_one;
> +
> struct io_mapped_region region;
> };
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2026-04-28 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 15:44 [PATCHSET 0/2] kbuf fixes Jens Axboe
2026-04-28 15:44 ` [PATCH 1/2] io_uring/kbuf: kill dead struct io_buffer_list 'nr_entries' member Jens Axboe
2026-04-28 17:54 ` Gabriel Krisman Bertazi
2026-04-28 15:44 ` [PATCH 2/2] io_uring/kbuf: support min length left for incremental buffers Jens Axboe
2026-04-28 17:53 ` Gabriel Krisman Bertazi [this message]
2026-04-28 18:02 ` Jens Axboe
2026-04-28 19:08 ` Gabriel Krisman Bertazi
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=87ik9bj7jt.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=code@mgjm.de \
--cc=io-uring@vger.kernel.org \
--cc=stable@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