Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 08 Mar 2019 15:16:37 -0800 (PST)
Message-Id: <20190308.151637.1852310112674993852.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
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20190306101353.9938-1-alazar@bitdefender.com>
References: <20190306101353.9938-1-alazar@bitdefender.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-2
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.