All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alazar@bitdefender.com
Cc: stefanha@redhat.com, sgarzare@redhat.com,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	aherghelegiu@bitdefender.com
Subject: Re: [PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
Date: Fri, 08 Mar 2019 15:16:37 -0800 (PST)	[thread overview]
Message-ID: <20190308.151637.1852310112674993852.davem@davemloft.net> (raw)
In-Reply-To: <20190306101353.9938-1-alazar@bitdefender.com>

From: Adalbert Lazăr <alazar@bitdefender.com>
Date: Wed,  6 Mar 2019 12:13:53 +0200

> Previous to commit 22b5c0b63f32 ("vsock/virtio: fix kernel panic
> after device hot-unplug"), vsock_core_init() was called from
> virtio_vsock_probe(). Now, virtio_transport_reset_no_sock() can be called
> before vsock_core_init() has the chance to run.
 ...
> Fixes: 22b5c0b63f32 ("vsock/virtio: fix kernel panic after device hot-unplug")
> Reported-by: Alexandru Herghelegiu <aherghelegiu@bitdefender.com>
> Signed-off-by: Adalbert Lazăr <alazar@bitdefender.com>
> Co-developed-by: Stefan Hajnoczi <stefanha@redhat.com>

Applied and queued up for -stable.

  parent reply	other threads:[~2019-03-08 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 10:13 [PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock Adalbert Lazăr
2019-03-07 16:37 ` Stefan Hajnoczi
2019-03-07 16:37 ` Stefan Hajnoczi
2019-03-07 19:12 ` Stefano Garzarella
2019-03-07 19:12 ` Stefano Garzarella
2019-03-08 23:16 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-06 10:13 Adalbert Lazăr

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=20190308.151637.1852310112674993852.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=aherghelegiu@bitdefender.com \
    --cc=alazar@bitdefender.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@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 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.