lp:~timg-tpi/ubuntu/+source/linux/+git/kinetic

Author: Dexuan Cui
Author Date: 2023-04-21 01:30:25 UTC

PCI: hv: Replace retarget_msi_interrupt_params with hyperv_pcpu_input_arg

BugLink: https://bugs.launchpad.net/bugs/2015369

4 commits are involved here:
A (2016): commit 0de8ce3ee8e3 ("PCI: hv: Allocate physically contiguous hypercall params buffer")
B (2017): commit be66b6736591 ("PCI: hv: Use page allocation for hbus structure")
C (2019): commit 877b911a5ba0 ("PCI: hv: Avoid a kmemleak false positive caused by the hbus buffer")
D (2018): commit 68bb7bfb7985 ("X86/Hyper-V: Enable IPI enlightenments")

Patch D introduced the per-CPU hypercall input page "hyperv_pcpu_input_arg"
in 2018. With patch D, we no longer need the per-Hyper-V-PCI-bus hypercall
input page "hbus->retarget_msi_interrupt_params" that was added in patch A,
and the issue addressed by patch B is no longer an issue, and we can also
get rid of patch C.

The change here is required for PCI device assignment to work for
Confidential VMs (CVMs) running without a paravisor, because otherwise we
would have to call set_memory_decrypted() for
"hbus->retarget_msi_interrupt_params" before calling the hypercall
HVCALL_RETARGET_INTERRUPT.

Signed-off-by: Dexuan Cui <decui@microsoft.com>
Reviewed-by: Michael Kelley <mikelley@microsoft.com>
Acked-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
Link: https://lore.kernel.org/r/20230421013025.17152-1-decui@microsoft.com
Signed-off-by: Wei Liu <wei.liu@kernel.org>
(cherry picked from commit a494aef23dfc732945cb42e22246a5c31174e4a5)
Signed-off-by: Dexuan Cui <decui@microsoft.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2023-05-04 09:09:23 UTC

5.19.0-1027.30~sf00357415.1

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Long Li
Author Date: 2023-02-16 00:32:02 UTC

RDMA/mana_ib: Fix a bug when the PF indicates more entries for registering memory on first packet

When registering memory in a large chunk that doesn't fit into a single PF
message, the PF may return GDMA_STATUS_MORE_ENTRIES on the first message if
there are more messages needed for registering more chunks.

Fix the VF to make it process the correct return code.

Fixes: 0266a177631d ("RDMA/mana_ib: Add a driver for Microsoft Azure Network Adapter")
Link: https://lore.kernel.org/r/1676507522-21018-1-git-send-email-longli@linuxonhyperv.com
Signed-off-by: Long Li <longli@microsoft.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
(cherry picked from commit 89d42b8c85b4c67d310c5ccaf491acbf71a260c3)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Haiyang Zhang
Author Date: 2023-04-12 21:16:03 UTC

net: mana: Add support for jumbo frame

BugLink: https://bugs.launchpad.net/bugs/2016898

During probe, get the hardware-allowed max MTU by querying the device
configuration. Users can select MTU up to the device limit.
When XDP is in use, limit MTU settings so the buffer size is within
one page. And, when MTU is set to a too large value, XDP is not allowed
to run.
Also, to prevent changing MTU fails, and leaves the NIC in a bad state,
pre-allocate all buffers before starting the change. So in low memory
condition, it will return error, without affecting the NIC.

Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit 80f6215b450eb8e92d8b1f117abf5ecf867f963e)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Baokun Li
Author Date: 2022-11-17 04:03:40 UTC

ext4: fix corrupt backup group descriptors after online resize

In commit 9a8c5b0d0615 ("ext4: update the backup superblock's at the end
of the online resize"), it is assumed that update_backups() only updates
backup superblocks, so each b_data is treated as a backupsuper block to
update its s_block_group_nr and s_checksum. However, update_backups()
also updates the backup group descriptors, which causes the backup group
descriptors to be corrupted.

The above commit fixes the problem of invalid checksum of the backup
superblock. The root cause of this problem is that the checksum of
ext4_update_super() is not set correctly. This problem has been fixed
in the previous patch ("ext4: fix bad checksum after online resize").

However, we do need to set block_group_nr for the backup superblock in
update_backups(). When a block is in a group that contains a backup
superblock, and the block is the first block in the group, the block is
definitely a superblock. We add a helper function that includes setting
s_block_group_nr and updating checksum, and then call it only when the
above conditions are met to prevent the backup group descriptors from
being incorrectly modified.

Fixes: 9a8c5b0d0615 ("ext4: update the backup superblock's at the end of the online resize")
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Reviewed-by: Jan Kara <jack@suse.cz>
Cc: stable@kernel.org
Link: https://lore.kernel.org/r/20221117040341.1380702-3-libaokun1@huawei.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
(cherry picked from commit 8f49ec603ae3e213bfab2799182724e3abac55a1)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Haiyang Zhang
Author Date: 2023-02-06 21:28:49 UTC

net: mana: Fix accessing freed irq affinity_hint

BugLink: https://bugs.launchpad.net/bugs/2007417

After calling irq_set_affinity_and_hint(), the cpumask pointer is
saved in desc->affinity_hint, and will be used later when reading
/proc/irq/<num>/affinity_hint. So the cpumask variable needs to be
persistent. Otherwise, we are accessing freed memory when reading
the affinity_hint file.

Also, need to clear affinity_hint before free_irq(), otherwise there
is a one-time warning and stack trace during module unloading:

 [ 243.948687] WARNING: CPU: 10 PID: 1589 at kernel/irq/manage.c:1913 free_irq+0x318/0x360
 ...
 [ 243.948753] Call Trace:
 [ 243.948754] <TASK>
 [ 243.948760] mana_gd_remove_irqs+0x78/0xc0 [mana]
 [ 243.948767] mana_gd_remove+0x3e/0x80 [mana]
 [ 243.948773] pci_device_remove+0x3d/0xb0
 [ 243.948778] device_remove+0x46/0x70
 [ 243.948782] device_release_driver_internal+0x1fe/0x280
 [ 243.948785] driver_detach+0x4e/0xa0
 [ 243.948787] bus_remove_driver+0x70/0xf0
 [ 243.948789] driver_unregister+0x35/0x60
 [ 243.948792] pci_unregister_driver+0x44/0x90
 [ 243.948794] mana_driver_exit+0x14/0x3fe [mana]
 [ 243.948800] __do_sys_delete_module.constprop.0+0x185/0x2f0

To fix the bug, use the persistent mask, cpumask_of(cpu#), and set
affinity_hint to NULL before freeing the IRQ, as required by free_irq().

Cc: stable@vger.kernel.org
Fixes: 71fa6887eeca ("net: mana: Assign interrupts to CPUs based on NUMA nodes")
Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
Reviewed-by: Michael Kelley <mikelley@microsoft.com>
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
Link: https://lore.kernel.org/r/1675718929-19565-1-git-send-email-haiyangz@microsoft.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 18a048370b06a3a521219e9e5b10bdc2178ef19c)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Haiyang Zhang
Author Date: 2022-12-02 19:43:10 UTC

net: mana: Fix race on per-CQ variable napi work_done

BugLink: https://bugs.launchpad.net/bugs/2003353

After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be
cleared, and another CPU can start napi thread and access per-CQ variable,
cq->work_done. If the other thread (for example, from busy_poll) sets
it to a value >= budget, this thread will continue to run when it should
stop, and cause memory corruption and panic.

To fix this issue, save the per-CQ work_done variable in a local variable
before napi_complete_done(), so it won't be corrupted by a possible
concurrent thread after napi_complete_done().

Also, add a flag bit to advertise to the NIC firmware: the NAPI work_done
variable race is fixed, so the driver is able to reliably support features
like busy_poll.

Cc: stable@vger.kernel.org
Fixes: e1b5683ff62e ("net: mana: Move NAPI from EQ to CQ")
Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
Link: https://lore.kernel.org/r/1670010190-28595-1-git-send-email-haiyangz@microsoft.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
(cherry picked from commit 18010ff776fa42340efc428b3ea6d19b3e7c7b21 linux-next)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Dexuan Cui
Author Date: 2023-01-10 03:50:27 UTC

UBUNTU: SAUCE: tdx: Drivers: hv: vmbus:: Fix the ARM64 build caused by recent TDX patches

BugLink: https://bugs.launchpad.net/bugs/2002658

Need to declare hv_isolation_type_tdx() for ARM64 as well.

PAGE_KERNEL_NOENC is only defined for x86, so let's still use
PAGE_KERNEL for ARM64.

Signed-off-by: Dexuan Cui <decui@microsoft.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Ronak Doshi
Author Date: 2022-07-27 17:30:37 UTC

vmxnet3: do not reschedule napi for rx processing

Commit '2c5a5748105a ("vmxnet3: add support for out of order rx
completion")' added support for out of order rx completion. Within
that patch, an enhancement was done to reschedule napi for processing
rx completions.

However, it can lead to missing an interrupt. So, this patch reverts
that part of the code.

Fixes: 2c5a5748105a ("vmxnet3: add support for out of order rx completion")
Signed-off-by: Ronak Doshi <doshir@vmware.com>
Acked-by: Guolin Yang <gyang@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit 5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Ronak Doshi
Author Date: 2022-07-27 17:30:37 UTC

vmxnet3: do not reschedule napi for rx processing

Commit '2c5a5748105a ("vmxnet3: add support for out of order rx
completion")' added support for out of order rx completion. Within
that patch, an enhancement was done to reschedule napi for processing
rx completions.

However, it can lead to missing an interrupt. So, this patch reverts
that part of the code.

Fixes: 2c5a5748105a ("vmxnet3: add support for out of order rx completion")
Signed-off-by: Ronak Doshi <doshir@vmware.com>
Acked-by: Guolin Yang <gyang@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit 5b91884bf50b21d34bd3daa5c8f8b7e92e0a2c46)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2022-09-06 18:37:27 UTC

5.19.0-1006.6~lp1971028.1

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Dimitri John Ledkov
Author Date: 2022-08-26 14:31:28 UTC

UBUNTU: [Config] Switch from DECOMP_SINGLE to DECOMP_MULTI_PERCPU

BugLink: https://bugs.launchpad.net/bugs/1980861

Overall MULTI_PERCPU has similar or better performance on the wide
range of instance types and squashfs filesystems.

Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Signed-off-by: Andrea Righi <andrea.righi@canonical.com>

Author: Paolo Pisati
Author Date: 2022-08-03 10:34:14 UTC

UBUNTU: Ubuntu-lowlatency-5.19.0-1003.3

Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>

Author: Paolo Pisati
Author Date: 2022-04-14 04:46:58 UTC

UBUNTU: Ubuntu-5.15.0-27.28

Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>

Author: Andrea Righi
Author Date: 2022-03-31 08:37:37 UTC

UBUNTU: Ubuntu-lowlatency-5.15.0-24.24

Signed-off-by: Andrea Righi <andrea.righi@canonical.com>