From: Dylan Yudaken <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
Dylan Yudaken <[email protected]>
Subject: [PATCH 0/2] io_uring: mshot read fix for buffer size changes
Date: Sun, 5 Nov 2023 22:30:06 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
This series fixes a bug (will send a liburing patch separately showing
it) where the used buffer size is clamped to the minimum of all the
previous buffers selected.
It also as part of this forces the multishot read API to set addr &
len to 0.
len should probably have some accounting post-processing if it has
meaning to set it to non-zero, but I think for a new API it is simpler
to overly-constrain it upfront?
addr is useful to force to zero as it will allow some more bits to be
used in `struct io_rw`, which is otherwise full.
Dylan Yudaken (2):
io_uring: do not allow multishot read to set addr or len
io_uring: do not clamp read length for multishot read
io_uring/rw.c | 9 +++++++++
1 file changed, 9 insertions(+)
--
2.41.0
next reply other threads:[~2023-11-05 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 22:30 Dylan Yudaken [this message]
2023-11-05 22:30 ` [PATCH 1/2] io_uring: do not allow multishot read to set addr or len Dylan Yudaken
2023-11-06 14:32 ` Jens Axboe
2023-11-06 14:51 ` Jens Axboe
2023-11-06 15:31 ` Dylan Yudaken
2023-11-05 22:30 ` [PATCH 2/2] io_uring: do not clamp read length for multishot read Dylan Yudaken
2023-11-06 14:46 ` Jens Axboe
2023-11-06 15:33 ` Dylan Yudaken
2023-11-06 15:46 ` Jens Axboe
2023-11-06 17:56 ` Jens Axboe
2023-11-06 20:35 ` [PATCH 0/2] io_uring: mshot read fix for buffer size changes 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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