From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>, io-uring <io-uring@vger.kernel.org>
Cc: Sung Keum <kambodi127@gmail.com>
Subject: Re: [PATCH] io_uring/kbuf: cap buffer selection length at MAX_RW_COUNT
Date: Sun, 26 Jul 2026 20:12:07 -0400 [thread overview]
Message-ID: <87v7a1cmug.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <aa826e79-ddc5-4a82-9863-a5edfdce709f@kernel.dk>
Jens Axboe <axboe@kernel.dk> writes:
> io_ring_buffers_peek() builds an iovec array from provided buffers, and
> that in turn can be handed off to a lower level provider. Be prudent and
> cap the total size to MAX_RW_COUNT, which is the Linux default for how
> much IO do to in a single call.
>
> No bugs here, but it's a good preventative measure to avoid truncation
> issues.
>
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>
next prev parent reply other threads:[~2026-07-27 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260727140454epcas5p1a2306b5a87d2ff6d299e89b0af320213@epcas5p1.samsung.com>
2026-07-26 22:28 ` [PATCH] io_uring/kbuf: cap buffer selection length at MAX_RW_COUNT Jens Axboe
2026-07-27 0:12 ` Gabriel Krisman Bertazi [this message]
2026-07-27 14:04 ` Nitesh Shetty
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=87v7a1cmug.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kambodi127@gmail.com \
/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