RE: [PATCH v1 1/1] virtio-block: switch to blk_get_max_hw_transfer

[Or Ozeri]

> -----Original Message-----
> From: Kevin Wolf <kwolf@redhat.com>
> Sent: Friday, 13 January 2023 13:45
> To: Ilya Dryomov <idryomov@gmail.com>
> Cc: Or Ozeri <ORO@il.ibm.com>; qemu-devel@nongnu.org;
> dupadhya@redhat.com; to.my.trociny@gmail.com; qemu-
> block@nongnu.org; Danny Harnik <DANNYH@il.ibm.com>; Stefan Hajnoczi
> <stefanha@redhat.com>; Paolo Bonzini <pbonzini@redhat.com>
> Subject: [EXTERNAL] Re: [PATCH v1 1/1] virtio-block: switch to
> blk_get_max_hw_transfer
> > 
> I'm not sure I understand. This is not a passthrough device (unlike scsi-
> generic), so why should we consider the hardware limits rather than the
> kernel/other backend limits for read/write requests?

I don't understand much about it as well :)
But anyway, this bug was tested on 6.1.0, and Ilya suggested that I will test 
it on newer versions.
After doing that, I found out that the bug is not reproduceable in 6.1.1.
The commit that fixed things in 6.1.1 is this:
block: introduce max_hw_iov for use in scsi-generic
https://lists.gnu.org/archive/html/qemu-block/2021-09/msg00807.html

I guess we can just discard this thread.

Thanks,
Or