Displaying 20 results from an estimated 20000 matches similar to: "[PATCH] drivers: vhost: vsock: fixed a brace coding style issue"
2018 Mar 09
0
[PATCH] drivers: vhost: vsock: fixed a brace coding style issue
On Fri, Mar 09, 2018 at 08:26:03AM +0530, Vaibhav Murkute wrote:
> Fixed a coding style issue.
>
> Signed-off-by: Vaibhav Murkute <vaibhavmurkute88 at gmail.com>
> ---
> drivers/vhost/vsock.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com>
-------------- next part --------------
A non-text attachment
2016 Sep 23
0
[PATCH] drivers: drm: nouveau: Fix brace coding style error
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
---
2020 May 14
0
[PATCH AUTOSEL 5.6 13/62] vhost/vsock: fix packet delivery order to monitoring devices
From: Stefano Garzarella <sgarzare at redhat.com>
[ Upstream commit 107bc0766b9feb5113074c753735a3f115c2141f ]
We want to deliver packets to monitoring devices before it is
put in the virtqueue, to avoid that replies can appear in the
packet capture before the transmitted packet.
Signed-off-by: Stefano Garzarella <sgarzare at redhat.com>
Signed-off-by: David S. Miller <davem at
2020 May 14
0
[PATCH AUTOSEL 5.4 12/49] vhost/vsock: fix packet delivery order to monitoring devices
From: Stefano Garzarella <sgarzare at redhat.com>
[ Upstream commit 107bc0766b9feb5113074c753735a3f115c2141f ]
We want to deliver packets to monitoring devices before it is
put in the virtqueue, to avoid that replies can appear in the
packet capture before the transmitted packet.
Signed-off-by: Stefano Garzarella <sgarzare at redhat.com>
Signed-off-by: David S. Miller <davem at
2020 May 14
0
[PATCH AUTOSEL 4.19 10/31] vhost/vsock: fix packet delivery order to monitoring devices
From: Stefano Garzarella <sgarzare at redhat.com>
[ Upstream commit 107bc0766b9feb5113074c753735a3f115c2141f ]
We want to deliver packets to monitoring devices before it is
put in the virtqueue, to avoid that replies can appear in the
packet capture before the transmitted packet.
Signed-off-by: Stefano Garzarella <sgarzare at redhat.com>
Signed-off-by: David S. Miller <davem at
2020 May 14
0
[PATCH AUTOSEL 4.14 17/39] vhost/vsock: fix packet delivery order to monitoring devices
From: Stefano Garzarella <sgarzare at redhat.com>
[ Upstream commit 107bc0766b9feb5113074c753735a3f115c2141f ]
We want to deliver packets to monitoring devices before it is
put in the virtqueue, to avoid that replies can appear in the
packet capture before the transmitted packet.
Signed-off-by: Stefano Garzarella <sgarzare at redhat.com>
Signed-off-by: David S. Miller <davem at
2020 Jun 08
0
[PATCH AUTOSEL 5.6 111/606] vhost/vsock: fix packet delivery order to monitoring devices
From: Stefano Garzarella <sgarzare at redhat.com>
[ Upstream commit 107bc0766b9feb5113074c753735a3f115c2141f ]
We want to deliver packets to monitoring devices before it is
put in the virtqueue, to avoid that replies can appear in the
packet capture before the transmitted packet.
Signed-off-by: Stefano Garzarella <sgarzare at redhat.com>
Signed-off-by: David S. Miller <davem at
2019 May 23
0
[PATCH 4.9 07/53] vsock/virtio: Initialize core virtio vsock before registering the driver
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
[
2019 May 23
0
[PATCH 4.14 09/77] vsock/virtio: Initialize core virtio vsock before registering the driver
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
[
2019 May 23
0
[PATCH 4.19 014/114] vsock/virtio: Initialize core virtio vsock before registering the driver
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
[
2019 May 23
0
[PATCH 5.0 014/139] vsock/virtio: Initialize core virtio vsock before registering the driver
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
[
2019 May 23
0
[PATCH 5.1 019/122] vsock/virtio: Initialize core virtio vsock before registering the driver
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
[
2019 May 16
2
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
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
2019 May 16
2
[PATCH RESEND] vsock/virtio: Initialize core virtio vsock before registering the driver
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
2017 Mar 02
2
[PATCH-v4-RESEND 1/4] vsock: track pkt owner vsock
From: Peng Tao <bergwolf at gmail.com>
Date: Wed, 1 Mar 2017 11:56:24 +0800
> So that we can cancel a queued pkt later if necessary.
>
> Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com>
> Signed-off-by: Peng Tao <bergwolf at gmail.com>
> ---
> include/linux/virtio_vsock.h | 2 ++
> net/vmw_vsock/virtio_transport_common.c | 7 +++++++
>
2017 Mar 02
2
[PATCH-v4-RESEND 1/4] vsock: track pkt owner vsock
From: Peng Tao <bergwolf at gmail.com>
Date: Wed, 1 Mar 2017 11:56:24 +0800
> So that we can cancel a queued pkt later if necessary.
>
> Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com>
> Signed-off-by: Peng Tao <bergwolf at gmail.com>
> ---
> include/linux/virtio_vsock.h | 2 ++
> net/vmw_vsock/virtio_transport_common.c | 7 +++++++
>
2019 May 22
0
Patch "vsock/virtio: Initialize core virtio vsock before registering the driver" has been added to the 5.0-stable tree
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
2019 May 22
0
Patch "vsock/virtio: Initialize core virtio vsock before registering the driver" has been added to the 5.1-stable tree
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
2019 May 22
0
Patch "vsock/virtio: Initialize core virtio vsock before registering the driver" has been added to the 4.19-stable tree
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
2019 May 22
0
Patch "vsock/virtio: Initialize core virtio vsock before registering the driver" has been added to the 4.14-stable tree
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