public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Keiichi Watanabe <keiichiw@chromium.org>
Cc: virtio-comment@lists.linux.dev, uekawa@chromium.org,
	takayas@chromium.org, dverkamp@chromium.org, tytso@google.com
Subject: Re: [PATCH 0/1] A new virtio-blk error code for host-side ENOSPC
Date: Tue, 18 Jun 2024 06:54:49 -0400	[thread overview]
Message-ID: <20240618064959-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240618081858.2795400-1-keiichiw@chromium.org>

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
> [2]: https://crrev.com/c/5599649
> [3]: https://crrev.com/c/5600325
> 

> *** BLURB HERE ***


it's a single patch, pls just send directly no cover letter needed.

> 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
> 


  parent reply	other threads:[~2024-06-18 10:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  8:18 [PATCH 0/1] A new virtio-blk error code for host-side ENOSPC Keiichi Watanabe
2024-06-18  8:18 ` [PATCH 1/1] virito-blk: Support NOSPC error Keiichi Watanabe
2024-06-18 10:58   ` Michael S. Tsirkin
2024-06-18 12:14     ` Michael S. Tsirkin
2024-06-18 11:54   ` Parav Pandit
2024-06-18 12:18     ` Michael S. Tsirkin
2024-06-19 13:09       ` Keiichi Watanabe
2024-07-03 22:54         ` Michael S. Tsirkin
2024-07-04  9:46           ` Parav Pandit
2024-07-04  8:04         ` Michael S. Tsirkin
2024-07-04  9:52           ` Parav Pandit
2024-07-04 11:19             ` Michael S. Tsirkin
2024-07-04 16:12               ` Parav Pandit
2024-06-18 10:54 ` Michael S. Tsirkin [this message]
2024-06-19 13:06   ` [PATCH 0/1] A new virtio-blk error code for host-side ENOSPC Keiichi Watanabe
2024-06-19 14:00 ` Stefan Hajnoczi
2024-07-03 22:55   ` Michael S. Tsirkin
2024-07-09 12:14     ` Stefan Hajnoczi
2024-07-09 13:31       ` Michael S. Tsirkin
2024-07-11  9:16         ` Stefan Hajnoczi

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 \
    --in-reply-to=20240618064959-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=dverkamp@chromium.org \
    --cc=keiichiw@chromium.org \
    --cc=takayas@chromium.org \
    --cc=tytso@google.com \
    --cc=uekawa@chromium.org \
    --cc=virtio-comment@lists.linux.dev \
    /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