Re: [PATCH 0/1] A new virtio-blk error code for host-side ENOSPC

[Stefan Hajnoczi <stefanha@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Tue, Jun 18, 2024 at 05:18:57PM +0900, Keiichi Watanabe wrote:
> This patch proposes a new error code VIRTIO_BLK_S_NOSPC to report
> the device's ENOSPC error to the driver so the driver can treat it
> in a different way from other IO errors.
> More motivation is explained in fs-devel mail [1].
> 
> [2] is a prototype implementation in crosvm and [3] is in virtio-blk
> driver. Idealy, the error should be propagated to the guest file system
> and handled smartly, but the part is still under discussion.
> 
> [1]: https://lore.kernel.org/linux-fsdevel/CAD90VcZybb0ZOVrhE-MqDPwEya8878uzA1RBwd68U7x4CufkTQ@mail.gmail.com/T/#u

I have replied on linux-fsdevel so we can discuss a bit more about the
context and get input from storage and file systems people.

Thanks,
Stefan

> [2]: https://crrev.com/c/5599649
> [3]: https://crrev.com/c/5600325
> 
> 
> *** BLURB HERE ***
> 
> Keiichi Watanabe (1):
>   virito-blk: Support NOSPC error
> 
>  device-types/blk/description.tex | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> -- 
> 2.45.2.627.g7a2c4fd464-goog
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]