From: Jens Axboe <[email protected]>
To: Keith Busch <[email protected]>,
[email protected], [email protected]
Cc: Keith Busch <[email protected]>
Subject: Re: [PATCH] io_uring: fix off-by one bvec index
Date: Mon, 20 Nov 2023 15:22:14 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/20/23 3:18 PM, Keith Busch wrote:
> From: Keith Busch <[email protected]>
>
> If the offset equals the bv_len of the first registered bvec, then the
> request does not include any of that first bvec. Skip it so that drivers
> don't have to deal with a zero length bvec, which was observed to break
> NVMe's PRP list creation.
Thanks Keith, that was fast (I sent in the report...). I applied this with
a fixes and stable tag.
--
Jens Axboe
next prev parent reply other threads:[~2023-11-20 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 22:18 [PATCH] io_uring: fix off-by one bvec index Keith Busch
2023-11-20 22:22 ` Jens Axboe [this message]
2023-11-21 14:42 ` 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] \
[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