similar to: [PATCH] drivers: vhost: vsock: fixed a brace coding style issue

From: Vaibhav Murkute <vaibhavmurkute88 at gmail.com> Date: Fri, 9 Mar 2018 08:26:03 +0530 > Fixed a coding style issue. > > Signed-off-by: Vaibhav Murkute <vaibhavmurkute88 at gmail.com> Applied to net-next, thanks.

Fixed a coding style issue. Else should follow brace. Signed-off-by: David Archuleta Jr. <darchuletajr at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_display.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_display.c b/drivers/gpu/drm/nouveau/nouveau_display.c index afbf557..0d39e17 100644 ---

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++

From: Ruslan Pisarev <ruslan at rpisarev.org.ua> Signed-off-by: Ruslan Pisarev <ruslan at rpisarev.org.ua> --- drivers/xen/xenbus/xenbus_probe.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c index 7397695..3b53452 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++

Re: placement of braces and "else" clauses. At the R prompt, I believe their placement must avoid causing a syntactically complete statement at the wrong place. This can results in what might be considered rather awkward looking code. IF it is known that code will be used via sourcing a script only, is there any potential problem with placing braces as shown below ? xxx <-

On Thu, May 16, 2019 at 01:51:07PM -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

From: "Jorge E. Moreira" <jemoreira at google.com> [ Upstream commit ba95e5dfd36647622d8897a2a0470dde60e59ffd ] 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 [

From: "Jorge E. Moreira" <jemoreira at google.com> [ Upstream commit ba95e5dfd36647622d8897a2a0470dde60e59ffd ] 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 [

From: "Jorge E. Moreira" <jemoreira at google.com> [ Upstream commit ba95e5dfd36647622d8897a2a0470dde60e59ffd ] 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 [

From: "Jorge E. Moreira" <jemoreira at google.com> [ Upstream commit ba95e5dfd36647622d8897a2a0470dde60e59ffd ] 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 [

From: "Jorge E. Moreira" <jemoreira at google.com> [ Upstream commit ba95e5dfd36647622d8897a2a0470dde60e59ffd ] 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 [

This is a note to let you know that I've just added the patch titled vsock/virtio: Initialize core virtio vsock before registering the driver to the 5.0-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: vsock-virtio-initialize-core-virtio-vsock-before-registering-the-driver.patch and

This is a note to let you know that I've just added the patch titled vsock/virtio: Initialize core virtio vsock before registering the driver to the 5.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: vsock-virtio-initialize-core-virtio-vsock-before-registering-the-driver.patch and

This is a note to let you know that I've just added the patch titled vsock/virtio: Initialize core virtio vsock before registering the driver to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: vsock-virtio-initialize-core-virtio-vsock-before-registering-the-driver.patch and

This is a note to let you know that I've just added the patch titled vsock/virtio: Initialize core virtio vsock before registering the driver to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: vsock-virtio-initialize-core-virtio-vsock-before-registering-the-driver.patch and

This is a note to let you know that I've just added the patch titled vsock/virtio: Initialize core virtio vsock before registering the driver to the 4.9-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: vsock-virtio-initialize-core-virtio-vsock-before-registering-the-driver.patch and

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

From: Stefan Hajnoczi <stefanha at redhat.com> The vsock_diag_test program directly included ../../../include/uapi/ headers from the source tree. Tests are supposed to use the usr/include/linux/ headers that have been prepared with make headers_install instead. Suggested-by: David S. Miller <davem at davemloft.net> Signed-off-by: Stefan Hajnoczi <stefanha at redhat.com>

On Fri, Jan 06, 2017 at 10:22:56AM +0800, Peng Tao wrote: > On Tue, Dec 13, 2016 at 5:50 PM, Stefan Hajnoczi <stefanha at gmail.com> wrote: > > On Mon, Dec 12, 2016 at 08:21:05PM +0800, Peng Tao wrote: > >> Currently, if a connect call fails on a signal or timeout (e.g., guest is still > >> in the process of starting up), we'll just return to caller and leave