From: Stefan Hajnoczi <stefanha@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, kernel-team@android.com,
stable@vger.kernel.org, "Jorge E. Moreira" <jemoreira@google.com>
Subject: Re: [PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
Date: Thu, 16 May 2019 10:16:39 +0100 [thread overview]
Message-ID: <20190516091639.GP29507@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190501003001.186239-1-jemoreira@google.com>
[-- Attachment #1: Type: text/plain, Size: 3541 bytes --]
On Tue, Apr 30, 2019 at 05:30:01PM -0700, Jorge E. Moreira wrote:
> Avoid a race in which static variables in net/vmw_vsock/af_vsock.c are
> accessed (while handling interrupts) before they are initialized.
>
> [ 4.201410] BUG: unable to handle kernel paging request at ffffffffffffffe8
> [ 4.207829] IP: vsock_addr_equals_addr+0x3/0x20
> [ 4.211379] PGD 28210067 P4D 28210067 PUD 28212067 PMD 0
> [ 4.211379] Oops: 0000 [#1] PREEMPT SMP PTI
> [ 4.211379] Modules linked in:
> [ 4.211379] CPU: 1 PID: 30 Comm: kworker/1:1 Not tainted 4.14.106-419297-gd7e28cc1f241 #1
> [ 4.211379] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
> [ 4.211379] Workqueue: virtio_vsock virtio_transport_rx_work
> [ 4.211379] task: ffffa3273d175280 task.stack: ffffaea1800e8000
> [ 4.211379] RIP: 0010:vsock_addr_equals_addr+0x3/0x20
> [ 4.211379] RSP: 0000:ffffaea1800ebd28 EFLAGS: 00010286
> [ 4.211379] RAX: 0000000000000002 RBX: 0000000000000000 RCX: ffffffffb94e42f0
> [ 4.211379] RDX: 0000000000000400 RSI: ffffffffffffffe0 RDI: ffffaea1800ebdd0
> [ 4.211379] RBP: ffffaea1800ebd58 R08: 0000000000000001 R09: 0000000000000001
> [ 4.211379] R10: 0000000000000000 R11: ffffffffb89d5d60 R12: ffffaea1800ebdd0
> [ 4.211379] R13: 00000000828cbfbf R14: 0000000000000000 R15: ffffaea1800ebdc0
> [ 4.211379] FS: 0000000000000000(0000) GS:ffffa3273fd00000(0000) knlGS:0000000000000000
> [ 4.211379] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 4.211379] CR2: ffffffffffffffe8 CR3: 000000002820e001 CR4: 00000000001606e0
> [ 4.211379] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 4.211379] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ 4.211379] Call Trace:
> [ 4.211379] ? vsock_find_connected_socket+0x6c/0xe0
> [ 4.211379] virtio_transport_recv_pkt+0x15f/0x740
> [ 4.211379] ? detach_buf+0x1b5/0x210
> [ 4.211379] virtio_transport_rx_work+0xb7/0x140
> [ 4.211379] process_one_work+0x1ef/0x480
> [ 4.211379] worker_thread+0x312/0x460
> [ 4.211379] kthread+0x132/0x140
> [ 4.211379] ? process_one_work+0x480/0x480
> [ 4.211379] ? kthread_destroy_worker+0xd0/0xd0
> [ 4.211379] ret_from_fork+0x35/0x40
> [ 4.211379] Code: c7 47 08 00 00 00 00 66 c7 07 28 00 c7 47 08 ff ff ff ff c7 47 04 ff ff ff ff c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 8b 47 08 <3b> 46 08 75 0a 8b 47 04 3b 46 04 0f 94 c0 c3 31 c0 c3 90 66 2e
> [ 4.211379] RIP: vsock_addr_equals_addr+0x3/0x20 RSP: ffffaea1800ebd28
> [ 4.211379] CR2: ffffffffffffffe8
> [ 4.211379] ---[ end trace f31cc4a2e6df3689 ]---
> [ 4.211379] Kernel panic - not syncing: Fatal exception in interrupt
> [ 4.211379] Kernel Offset: 0x37000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
> [ 4.211379] Rebooting in 5 seconds..
>
> Fixes: 22b5c0b63f32 ("vsock/virtio: fix kernel panic after device hot-unplug")
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: kvm@vger.kernel.org
> Cc: virtualization@lists.linux-foundation.org
> Cc: netdev@vger.kernel.org
> Cc: kernel-team@android.com
> Cc: stable@vger.kernel.org [4.9+]
> Signed-off-by: Jorge E. Moreira <jemoreira@google.com>
> ---
> net/vmw_vsock/virtio_transport.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
This patch is good to go, I've posted my R-b downthread.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-05-16 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 0:30 [PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver Jorge E. Moreira
2019-05-01 19:08 ` Stefan Hajnoczi
2019-05-02 8:20 ` Stefano Garzarella
2019-05-06 20:19 ` Jorge Moreira Broche
2019-05-07 12:25 ` Stefano Garzarella
2019-05-15 15:24 ` Stefan Hajnoczi
2019-05-16 7:48 ` Stefano Garzarella
2019-05-16 9:14 ` Stefan Hajnoczi
2019-05-16 9:16 ` Stefan Hajnoczi [this message]
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=20190516091639.GP29507@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=davem@davemloft.net \
--cc=jemoreira@google.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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).