[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190308.151637.1852310112674993852.davem@davemloft.net>
Date: Fri, 08 Mar 2019 15:16:37 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: alazar@...defender.com
Cc: stefanha@...hat.com, sgarzare@...hat.com,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
aherghelegiu@...defender.com
Subject: Re: [PATCH v2] vsock/virtio: fix kernel panic from
virtio_transport_reset_no_sock
From: Adalbert Lazăr <alazar@...defender.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@...defender.com>
> Signed-off-by: Adalbert Lazăr <alazar@...defender.com>
> Co-developed-by: Stefan Hajnoczi <stefanha@...hat.com>
Applied and queued up for -stable.
Powered by blists - more mailing lists