diff options
| author | Stefan Hajnoczi | 2022-07-06 10:03:41 +0200 |
|---|---|---|
| committer | Stefan Hajnoczi | 2022-07-07 10:04:15 +0200 |
| commit | be6a166fde652589761cf70471bcde623e9bd72a (patch) | |
| tree | e1baac746a39c68813c441da727548379b76fc41 /scripts | |
| parent | io_uring: fix short read slow path (diff) | |
| download | qemu-be6a166fde652589761cf70471bcde623e9bd72a.tar.gz qemu-be6a166fde652589761cf70471bcde623e9bd72a.tar.xz qemu-be6a166fde652589761cf70471bcde623e9bd72a.zip | |
block/io_uring: clarify that short reads can happen
Jens Axboe has confirmed that short reads are rare but can happen:
https://lore.kernel.org/io-uring/YsU%2FCGkl9ZXUI+Tj@stefanha-x1.localdomain/T/#m729963dc577d709b709c191922e98ec79d7eef54
The luring_resubmit_short_read() comment claimed they were only due to a
specific io_uring bug that was fixed in Linux commit 9d93a3f5a0c
("io_uring: punt short reads to async context"), which is wrong.
Dominique Martinet found that a btrfs bug also causes short reads. There
may be more kernel code paths that result in short reads.
Let's consider short reads fair game.
Cc: Dominique Martinet <dominique.martinet@atmark-techno.com>
Based-on: <20220630010137.2518851-1-dominique.martinet@atmark-techno.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Message-id: 20220706080341.1206476-1-stefanha@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions