linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: 李东升 <lidongsheng@dayudpu.com>
Cc: mst <mst@redhat.com>,
	virtualization <virtualization@lists.linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virtio_vdpa: Support surprise removal of virtio vdpa device
Date: Tue, 11 Jan 2022 12:37:49 +0800	[thread overview]
Message-ID: <CACGkMEvPnsDHn_gUdq2g2_Xzzqp8KVVhpaApnssYT9NT=mgm1A@mail.gmail.com> (raw)
In-Reply-To: <tencent_7A45E1E967F13AE14B061269@qq.com>

On Tue, Jan 11, 2022 at 11:38 AM 李东升 <lidongsheng@dayudpu.com> wrote:
>
> When virtio vdpa device removed, the abnormal damage of the device cannot be
> perceived normally, which will cause problems similar to:
>
> 43bb40c5b926
>
> Hence, add the ability to abort the command on surprise removal
>
> Signed-off-by: dongsheng li <lidongsheng@dayudpu.com>

Acked-by: Jason Wang <jasowang@redhat.com>

> ---
>  drivers/virtio/virtio_vdpa.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/virtio/virtio_vdpa.c b/drivers/virtio/virtio_vdpa.c
> index 4a9ddb44b2a7..fd930409d190 100644
> --- a/drivers/virtio/virtio_vdpa.c
> +++ b/drivers/virtio/virtio_vdpa.c
> @@ -374,6 +374,7 @@ static void virtio_vdpa_remove(struct vdpa_device *vdpa)
>  {
>   struct virtio_vdpa_device *vd_dev = vdpa_get_drvdata(vdpa);
>
> + virtio_break_device(vd_dev->vdev);
>   unregister_virtio_device(&vd_dev->vdev);
>  }
>
> --
> 2.17.1


       reply	other threads:[~2022-01-11  4:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_7A45E1E967F13AE14B061269@qq.com>
2022-01-11  4:37 ` Jason Wang [this message]
2022-01-11 11:52 ` [PATCH] virtio_vdpa: Support surprise removal of virtio vdpa device Michael S. Tsirkin
2022-01-12  2:23   ` Jason Wang
2022-01-12  6:30     ` Michael S. Tsirkin
2022-01-12  7:52       ` Jason Wang
2022-01-12 14:52         ` Michael S. Tsirkin
     [not found]       ` <tencent_18F8A88D22E327230EF313BE@qq.com>
2022-01-12 15:02         ` Michael S. Tsirkin
2022-01-11  4:08 dongsheng li

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='CACGkMEvPnsDHn_gUdq2g2_Xzzqp8KVVhpaApnssYT9NT=mgm1A@mail.gmail.com' \
    --to=jasowang@redhat.com \
    --cc=lidongsheng@dayudpu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).