From: Jens Axboe <[email protected]>
To: [email protected], Dylan Yudaken <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2 0/3] io_uring: mshot read fix for buffer size changes
Date: Mon, 06 Nov 2023 13:42:49 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 06 Nov 2023 20:39:06 +0000, Dylan Yudaken wrote:
> This series fixes a bug (see [1] for liburing patch)
> 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?
>
> [...]
Applied, thanks!
[1/3] io_uring: indicate if io_kbuf_recycle did recycle anything
commit: 89d528ba2f8281de61163c6b62e598b64d832175
[2/3] io_uring: do not allow multishot read to set addr or len
commit: 49fbe99486786661994a55ced855c31d966bbdf0
[3/3] io_uring: do not clamp read length for multishot read
commit: e53759298a7d7e98c3e5c2440d395d19cea7d6bf
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-11-06 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 20:39 [PATCH v2 0/3] io_uring: mshot read fix for buffer size changes Dylan Yudaken
2023-11-06 20:39 ` [PATCH v2 1/3] io_uring: indicate if io_kbuf_recycle did recycle anything Dylan Yudaken
2023-11-06 20:39 ` [PATCH v2 2/3] io_uring: do not allow multishot read to set addr or len Dylan Yudaken
2023-11-06 20:39 ` [PATCH v2 3/3] io_uring: do not clamp read length for multishot read Dylan Yudaken
2023-11-06 20:42 ` Jens Axboe [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=169930336907.203554.16139866523353846821.b4-ty@kernel.dk \
[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