search for: 22b5c0b63f32

Displaying 20 results from an estimated 31 matches for "22b5c0b63f32".

[PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
2019 Mar 06
2
[PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
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. [Wed Feb 27 14:17:09 2019] BUG: unable to handle kernel NULL pointer der...
[PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
2019 Mar 06
2
[PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
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. [Wed Feb 27 14:17:09 2019] BUG: unable to handle kernel NULL pointer der...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 15
2
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...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 at redhat.com> > > > > > Cc: "David S. Miller" <davem at davemloft.net> > > > > > Cc: kvm at vger.kernel.org > > >...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 15
2
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...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 at redhat.com> > > > > > Cc: "David S. Miller" <davem at davemloft.net> > > > > > Cc: kvm at vger.kernel.org > > >...
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 16
2
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
...ffe8 [ 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 at redhat.com> Cc: Stefano Garzarella <sgarzare at redhat.com> Cc: "David S. Miller" <davem at davemloft.net> Cc: kvm at vger.kernel.org Cc: virtualization at lists.linux-f...
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 16
2
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
...ffe8 [ 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 at redhat.com> Cc: Stefano Garzarella <sgarzare at redhat.com> Cc: "David S. Miller" <davem at davemloft.net> Cc: kvm at vger.kernel.org Cc: virtualization at lists.linux-f...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 02
2
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...9 ]--- > > [ 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 at redhat.com> > > Cc: "David S. Miller" <davem at davemloft.net> > > Cc: kvm at vger.kernel.org > > Cc: virtualization at lists.linux-foundation.org...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 02
2
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...9 ]--- > > [ 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 at redhat.com> > > Cc: "David S. Miller" <davem at davemloft.net> > > Cc: kvm at vger.kernel.org > > Cc: virtualization at lists.linux-foundation.org...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 01
3
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...ffe8 [ 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 at redhat.com> Cc: "David S. Miller" <davem at davemloft.net> Cc: kvm at vger.kernel.org Cc: virtualization at lists.linux-foundation.org Cc: netdev at vger.kernel.org Cc: kernel...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 01
3
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...ffe8 [ 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 at redhat.com> Cc: "David S. Miller" <davem at davemloft.net> Cc: kvm at vger.kernel.org Cc: virtualization at lists.linux-foundation.org Cc: netdev at vger.kernel.org Cc: kernel...
[PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
2019 Mar 07
0
[PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
On Wed, Mar 06, 2019 at 12:13:53PM +0200, Adalbert Laz?r wrote: > 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. > > [Wed Feb 27 14:17:09 2019] BUG: unable to handl...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 06
1
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...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 at redhat.com> > > > Cc: "David S. Miller" <davem at davemloft.net> > > > Cc: kvm at vger.kernel.org > > > Cc: virtualization at lists.l...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 07
0
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...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 at redhat.com> > > > > Cc: "David S. Miller" <davem at davemloft.net> > > > > Cc: kvm at vger.kernel.org > > > > Cc: virtu...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 16
0
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...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 at redhat.com> > > > > > > Cc: "David S. Miller" <davem at davemloft.net> > > > > > > Cc: kvm at vger.kernel.org...
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 18
0
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
From: "Jorge E. Moreira" <jemoreira at google.com> Date: Thu, 16 May 2019 13:51:07 -0700 > Avoid a race in which static variables in net/vmw_vsock/af_vsock.c are > accessed (while handling interrupts) before they are initialized. ... > Fixes: 22b5c0b63f32 ("vsock/virtio: fix kernel panic after device hot-unplug") > Cc: Stefan Hajnoczi <stefanha at redhat.com> > Cc: Stefano Garzarella <sgarzare at redhat.com> > Cc: "David S. Miller" <davem at davemloft.net> > Cc: kvm at vger.kernel.org > Cc: virtua...
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 16
0
[PATCH] vsock/virtio: Initialize core virtio vsock before registering the driver
...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 at redhat.com> > Cc: "David S. Miller" <davem at davemloft.net> > Cc: kvm at vger.kernel.org > Cc: virtualization at lists.linux-foundation.org > Cc: netdev at v...
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 17
0
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
...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 at redhat.com> > Cc: Stefano Garzarella <sgarzare at redhat.com> > Cc: "David S. Miller" <davem at davemloft.net> > Cc: kvm at vger.kernel.org > Cc: virtua...
[PATCH 4.9 07/53] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 23
0
[PATCH 4.9 07/53] vsock/virtio: Initialize core virtio vsock before registering the driver
...ffe8 [ 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 at redhat.com> Cc: Stefano Garzarella <sgarzare at redhat.com> Cc: "David S. Miller" <davem at davemloft.net> Cc: kvm at vger.kernel.org Cc: virtualization at lists.linux-f...
[PATCH 4.14 09/77] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 23
0
[PATCH 4.14 09/77] vsock/virtio: Initialize core virtio vsock before registering the driver
...ffe8 [ 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 at redhat.com> Cc: Stefano Garzarella <sgarzare at redhat.com> Cc: "David S. Miller" <davem at davemloft.net> Cc: kvm at vger.kernel.org Cc: virtualization at lists.linux-f...
[PATCH 4.19 014/114] vsock/virtio: Initialize core virtio vsock before registering the driver
2019 May 23
0
[PATCH 4.19 014/114] vsock/virtio: Initialize core virtio vsock before registering the driver
...ffe8 [ 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 at redhat.com> Cc: Stefano Garzarella <sgarzare at redhat.com> Cc: "David S. Miller" <davem at davemloft.net> Cc: kvm at vger.kernel.org Cc: virtualization at lists.linux-f...