All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gautam Dawar <gdawar.xilinx@gmail.com>
Cc: martinh@xilinx.com, hanand@xilinx.com, gdawar@xilinx.com,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2] vhost vdpa: fix the missing irq_bypass_unregister_producer() invocation
Date: Tue, 23 Feb 2021 07:12:54 -0500	[thread overview]
Message-ID: <20210223071149-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJ-rMYpFFD0vwERMbj_tMLmeFqECr0Q+s4ct_sO0AAt3rgWG0Q@mail.gmail.com>

On Tue, Feb 23, 2021 at 03:30:45PM +0530, Gautam Dawar wrote:
> When qemu with vhost-vdpa netdevice is run for the first time, it works well.
> But after the VM is powered off, the next qemu run causes kernel panic due to a
> NULL pointer dereference in irq_bypass_register_producer().
> 
> When the VM is powered off, vhost_vdpa_clean_irq() misses on calling
> irq_bypass_unregister_producer() for irq 0 because of the existing check.
> 
> This leaves stale producer nodes, which are reset in vhost_vring_call_reset()
> when vhost_dev_init() is invoked during the second qemu run.
> 
> As the node member of struct irq_bypass_producer is also initialized
> to zero, traversal on the producers list causes crash due to NULL pointer
> dereference.
> 
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=211711
> Signed-off-by: Gautam Dawar <gdawar@xilinx.com>

Could you please repost without HTML? Otherwise git am fails on this patch:

error: corrupt patch at line 6
error: could not build fake ancestor
Patch failed at 0001 vhost vdpa: fix the missing irq_bypass_unregister_producer() invocation

Also, which commit introduces the bug? A Fixes: tag would be helpful.

Thanks!

> -----
> changelog:
> v1->v2:
>  - Addressed Jason's comment to remove the irq check and use
>    vhost_vdpa_unsetup_vq_irq() to avoid local variable vq
> -----
> 
> 
> diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c
> index 62a9bb0efc55..e00573b87aba 100644
> --- a/drivers/vhost/vdpa.c
> +++ b/drivers/vhost/vdpa.c
> @@ -844,14 +844,10 @@ static int vhost_vdpa_open(struct inode *inode, struct
> file *filep)
> 
>  static void vhost_vdpa_clean_irq(struct vhost_vdpa *v)
>  {
> -       struct vhost_virtqueue *vq;
>         int i;
> 
> -       for (i = 0; i < v->nvqs; i++) {
> -               vq = &v->vqs[i];
> -               if (vq->call_ctx.producer.irq)
> -                       irq_bypass_unregister_producer(&vq->call_ctx.producer);
> -       }
> +       for (i = 0; i < v->nvqs; i++)
> +               vhost_vdpa_unsetup_vq_irq(v, i);
>  }
> 
>  static int vhost_vdpa_release(struct inode *inode, struct file *filep)

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2021-02-23 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 10:00 [PATCH v2] vhost vdpa: fix the missing irq_bypass_unregister_producer() invocation Gautam Dawar
2021-02-23 10:13 ` Jason Wang
2021-02-23 12:12 ` Michael S. Tsirkin [this message]
2021-02-23 12:46   ` Gautam Dawar

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=20210223071149-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=gdawar.xilinx@gmail.com \
    --cc=gdawar@xilinx.com \
    --cc=hanand@xilinx.com \
    --cc=martinh@xilinx.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 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.