From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "stefanha@redhat.com" <stefanha@redhat.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"NBU-Contact-Li Rongqing (EXTERNAL)" <lirongqing@baidu.com>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Israel Rukshin <israelr@nvidia.com>
Subject: Re: [PATCH v1] virtio_blk: Fix disk deletion hang on device surprise removal
Date: Wed, 21 May 2025 12:49:51 -0400 [thread overview]
Message-ID: <20250521124926-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CY8PR12MB7195200C1F5D877448DF1D3BDC9EA@CY8PR12MB7195.namprd12.prod.outlook.com>
On Wed, May 21, 2025 at 12:40:10PM +0000, Parav Pandit wrote:
> > You can include this in the series if you like. Tweak to taste:
> >
> Thanks for the patch. This virtio core comment update can be done at later point without fixes tag.
> Will park for the later.
no problem with that, either.
next prev parent reply other threads:[~2025-05-21 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 6:37 [PATCH v1] virtio_blk: Fix disk deletion hang on device surprise removal Parav Pandit
2025-05-21 8:17 ` Michael S. Tsirkin
2025-05-21 9:14 ` Parav Pandit
2025-05-21 9:18 ` Parav Pandit
2025-05-21 9:22 ` Michael S. Tsirkin
2025-05-21 9:19 ` Michael S. Tsirkin
2025-05-21 9:32 ` Parav Pandit
2025-05-21 10:16 ` Michael S. Tsirkin
2025-05-21 10:34 ` Parav Pandit
2025-05-21 10:43 ` Michael S. Tsirkin
2025-05-21 12:40 ` Parav Pandit
2025-05-21 16:49 ` Michael S. Tsirkin [this message]
2025-05-21 14:56 ` Stefan Hajnoczi
2025-05-22 2:57 ` Parav Pandit
2025-05-22 14:36 ` Stefan Hajnoczi
2025-05-22 14:55 ` Parav Pandit
2025-05-22 18:12 ` Stefan Hajnoczi
2025-05-22 18:58 ` Parav Pandit
2025-05-26 9:23 ` Parav Pandit
2025-05-26 13:29 ` 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=20250521124926-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=israelr@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mgurtovoy@nvidia.com \
--cc=parav@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.