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

Author: Tim Gardner
Author Date: 2023-08-08 15:47:34 UTC

6.2.0-1010.10~sf00365762.1

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

Author: Tim Gardner
Author Date: 2023-08-08 14:58:40 UTC

6.2.0-1010.10~sf00365760.1

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

Author: Dexuan Cui
Author Date: 2023-07-10 18:36:04 UTC

UBUNTU: SAUCE: Fix building ARM64

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

(cherry picked from commit 1727b08420f8909333573aaa67e1aa8738d4fb88 https://github.com/dcui/linux)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Doug Berger
Author Date: 2023-04-14 21:29:25 UTC

swiotlb: relocate PageHighMem test away from rmem_swiotlb_setup

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

The reservedmem_of_init_fn's are invoked very early at boot before the
memory zones have even been defined. This makes it inappropriate to test
whether the page corresponding to a PFN is in ZONE_HIGHMEM from within
one.

Removing the check allows an ARM 32-bit kernel with SPARSEMEM enabled to
boot properly since otherwise we would be de-referencing an
uninitialized sparsemem map to perform pfn_to_page() check.

The arm64 architecture happens to work (and also has no high memory) but
other 32-bit architectures could also be having similar issues.

While it would be nice to provide early feedback about a reserved DMA
pool residing in highmem, it is not possible to do that until the first
time we try to use it, which is where the check is moved to.

Fixes: 0b84e4f8b793 ("swiotlb: Add restricted DMA pool initialization")
Signed-off-by: Doug Berger <opendmb@gmail.com>
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
(cherry picked from commit a90922fa25370902322e9de6640e58737d459a50)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Dexuan Cui
Author Date: 2023-04-20 01:50:27 UTC

PCI: hv: Use async probing to reduce boot time

BugLink: https://bugs.launchpad.net/bugs/2023071
BugLink: https://bugs.launchpad.net/bugs/2023594

Commit 414428c5da1c ("PCI: hv: Lock PCI bus on device eject") added
pci_lock_rescan_remove() and pci_unlock_rescan_remove() in
create_root_hv_pci_bus() and in hv_eject_device_work() to address the
race between create_root_hv_pci_bus() and hv_eject_device_work(), but it
turns that grabing the pci_rescan_remove_lock mutex is not enough:
refer to the earlier fix "PCI: hv: Add a per-bus mutex state_lock".

Now with hbus->state_lock and other fixes, the race is resolved, so
remove pci_{lock,unlock}_rescan_remove() in create_root_hv_pci_bus():
this removes the serialization in hv_pci_probe() and hence allows
async-probing (PROBE_PREFER_ASYNCHRONOUS) to work.

Add the async-probing flag to hv_pci_drv.

pci_{lock,unlock}_rescan_remove() in hv_eject_device_work() and in
hv_pci_remove() are still kept: according to the comment before
drivers/pci/probe.c: static DEFINE_MUTEX(pci_rescan_remove_lock),
"PCI device removal routines should always be executed under this mutex".

Signed-off-by: Dexuan Cui <decui@microsoft.com>
Reviewed-by: Michael Kelley <mikelley@microsoft.com>
Reviewed-by: Long Li <longli@microsoft.com>
Cc: stable@vger.kernel.org
(cherry picked from commit 08a9019ea35582f310946d193e5daab53931fd04 https://github.com/dcui/tdx.git)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Michael Kelley
Author Date: 2023-05-23 16:38:27 UTC

arm64/hyperv: Use CPUHP_AP_HYPERV_ONLINE state to fix CPU online sequencing

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

State CPUHP_AP_HYPERV_ONLINE has been introduced to correctly sequence the
initialization of hyperv_pcpu_input_arg. Use this new state for Hyper-V
initialization so that hyperv_pcpu_input_arg is allocated early enough.

Signed-off-by: Michael Kelley <mikelley@microsoft.com>
(cherry picked from commit 2cd655fda96ea765db6b4145f7828280a0cfa2a1 https://github.com/kelleymh/linux.git)
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

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 linux-next)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Andrea Righi
Author Date: 2023-04-14 14:57:48 UTC

UBUNTU: Ubuntu-azure-6.2.0-1004.4

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

Author: Paolo Pisati
Author Date: 2022-06-15 14:02:02 UTC

UBUNTU: Ubuntu-azure-5.18.0-1002.2

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