Message ID | 20231120221831.2646460-1-kbusch@meta.com (mailing list archive) |
---|---|
State | New |
Headers | show |
Series | io_uring: fix off-by one bvec index | expand |
On 11/20/23 3:18 PM, Keith Busch wrote: > From: Keith Busch <kbusch@kernel.org> > > 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.
On Mon, 20 Nov 2023 14:18:31 -0800, Keith Busch wrote: > 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. > > Applied, thanks! [1/1] io_uring: fix off-by one bvec index commit: d6fef34ee4d102be448146f24caf96d7b4a05401 Best regards,
diff --git a/io_uring/rsrc.c b/io_uring/rsrc.c index 7034be555334d..f521c5965a933 100644 --- a/io_uring/rsrc.c +++ b/io_uring/rsrc.c @@ -1258,7 +1258,7 @@ int io_import_fixed(int ddir, struct iov_iter *iter, */ const struct bio_vec *bvec = imu->bvec; - if (offset <= bvec->bv_len) { + if (offset < bvec->bv_len) { /* * Note, huge pages buffers consists of one large * bvec entry and should always go this way. The other