[PATCH v4] Drivers: hv: Cosmetic changes for hv.c and balloon.c

2024-04-22 Thread Aditya Nagesh
Fix issues reported by checkpatch.pl script in hv.c and balloon.c - Remove unnecessary parentheses - Remove extra newlines - Remove extra spaces - Add spaces between comparison operators - Remove comparison with NULL in if statements No functional changes intended Signed-off-by: Aditya Nages

[PATCH AUTOSEL 6.1 18/19] Drivers: hv: vmbus: Don't free ring buffers that couldn't be re-encrypted

2024-04-22 Thread Sasha Levin
From: Michael Kelley [ Upstream commit 30d18df6567be09c1433e81993e35e3da573ac48 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.1 17/19] uio_hv_generic: Don't free decrypted memory

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 3d788b2fbe6a1a1a9e3db09742b90809d51638b7 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.1 16/19] Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 211f514ebf1ef5de37b1cf6df9d28a56cfd242ca ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.6 27/29] Drivers: hv: vmbus: Don't free ring buffers that couldn't be re-encrypted

2024-04-22 Thread Sasha Levin
From: Michael Kelley [ Upstream commit 30d18df6567be09c1433e81993e35e3da573ac48 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.6 26/29] uio_hv_generic: Don't free decrypted memory

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 3d788b2fbe6a1a1a9e3db09742b90809d51638b7 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.6 25/29] hv_netvsc: Don't free decrypted memory

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit bbf9ac34677b57506a13682b31a2a718934c0e31 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.6 24/29] Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 211f514ebf1ef5de37b1cf6df9d28a56cfd242ca ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.6 23/29] Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 03f5a999adba062456c8c818a683beb1b498983a ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.8 39/43] Drivers: hv: vmbus: Don't free ring buffers that couldn't be re-encrypted

2024-04-22 Thread Sasha Levin
From: Michael Kelley [ Upstream commit 30d18df6567be09c1433e81993e35e3da573ac48 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.8 38/43] uio_hv_generic: Don't free decrypted memory

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 3d788b2fbe6a1a1a9e3db09742b90809d51638b7 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.8 37/43] hv_netvsc: Don't free decrypted memory

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit bbf9ac34677b57506a13682b31a2a718934c0e31 ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.8 36/43] Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 211f514ebf1ef5de37b1cf6df9d28a56cfd242ca ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

[PATCH AUTOSEL 6.8 35/43] Drivers: hv: vmbus: Leak pages if set_memory_encrypted() fails

2024-04-22 Thread Sasha Levin
From: Rick Edgecombe [ Upstream commit 03f5a999adba062456c8c818a683beb1b498983a ] In CoCo VMs it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to ha

Re: [PATCH] hv/vmbus_drv: rename hv_acpi_init() to vmbus_init()

2024-04-22 Thread Wei Liu
On Thu, Apr 18, 2024 at 10:56:49PM -0700, Erni Sri Satya Vennela wrote: > As the driver now supports both ACPI and DeviceTree, > rename hv_acpi_init() to vmbus_init() and > change comments accordingly. > > Signed-off-by: Erni Sri Satya Vennela Applied. Thanks.

Re: [PATCH] x86/hyperv: Consider NUMA affinity when allocating memory for per-CPU vmsa

2024-04-22 Thread Wei Liu
On Mon, Apr 15, 2024 at 04:57:12PM +0800, Li RongQing wrote: > per-CPU vmsa are dominantly accessed from their own local CPUs, > so allocate them node-local to improve performance. > > And reorganized variables to be reverse christmas tree order > > Signed-off-by: Li RongQing Applied. Thanks.

Re: [PATCH v2] Add a header in ifcfg and nm keyfiles describing the owner of the files

2024-04-22 Thread Wei Liu
On Thu, Apr 18, 2024 at 05:35:49PM +0530, Ani Sinha wrote: > A comment describing the source of writing the contents of the ifcfg and > network manager keyfiles (hyperv kvp daemon) is useful. It is valuable both > for debugging as well as for preventing users from modifying them. > > CC: shradhagu

Re: [PATCH net-next] net: mana: Add new device attributes for mana

2024-04-22 Thread Shradha Gupta
On Fri, Apr 19, 2024 at 08:51:02PM +0200, Andrew Lunn wrote: > On Fri, Apr 19, 2024 at 09:59:26AM -0700, Shradha Gupta wrote: > > On Thu, Apr 18, 2024 at 08:42:59PM +0200, Andrew Lunn wrote: > > > > >From an RDMA perspective this is all available from other APIs already > > > > at least and I would