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

Author: Tim Gardner
Author Date: 2023-10-23 13:03:55 UTC

6.2.0-1016.16~22.04.2.lp2040163

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

Author: Steve French
Author Date: 2023-08-17 04:25:29 UTC

smb: client: fix null auth

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

Commit abdb1742a312 removed code that clears ctx->username when sec=none, so attempting
to mount with '-o sec=none' now fails with -EACCES. Fix it by adding that logic to the
parsing of the 'sec' option, as well as checking if the mount is using null auth before
setting the username when parsing the 'user' option.

Fixes: abdb1742a312 ("cifs: get rid of mount options string parsing")
Cc: stable@vger.kernel.org
Signed-off-by: Scott Mayhew <smayhew@redhat.com>
Reviewed-by: Paulo Alcantara (SUSE) <pc@manguebit.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
(cherry picked from commit da531277a9a02ed050bdcce92939d08931db3248 git://git.samba.org/sfrench/cifs-2.6.git)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2023-09-12 14:22:49 UTC

5.15.0-1049.56~lp2034745.1

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

Author: Tim Gardner
Author Date: 2023-08-23 12:55:22 UTC

6.2.0-1010.10~22.04.2.lp2028286.1

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

Author: Tim Gardner
Author Date: 2023-08-08 15:46:28 UTC

5.15.0-1045.52~sf00365762.1

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

Author: Tim Gardner
Author Date: 2023-08-08 15:01:31 UTC

5.15.0-1045.52~sf00365760.1

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

Author: Tim Gardner
Author Date: 2023-08-03 16:40:05 UTC

5.15.0-1045.52~sf00365185.1

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

Author: Tim Gardner
Author Date: 2023-07-13 12:18:48 UTC

5.15.0-1043.50~sf00358953.1

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

Author: Tim Gardner
Author Date: 2023-07-10 15:14:28 UTC

6.2.0-1008.8~22.04.1.lp2026736.1

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
(backported from commit 08a9019ea35582f310946d193e5daab53931fd04 https://github.com/dcui/tdx.git)
[rtg - context adjustments]
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2023-05-08 12:40:42 UTC

5.15.0-1039.46~sf00357415.2

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

Author: Tim Gardner
Author Date: 2023-05-04 09:51:38 UTC

5.19.0-1026.29~22.04.2.sf00357415.1

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

Author: Tim Gardner
Author Date: 2023-04-24 18:48:22 UTC

UBUNTU: Ubuntu-azure-6.2-6.2.0-1004.4~22.04.1

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

Author: Tim Gardner
Author Date: 2023-04-05 18:23:35 UTC

5.19.0-1024.25~22.04.1.sf00357415.1

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

Author: Tim Gardner
Author Date: 2023-04-05 18:19:42 UTC

5.15.0-1037.44~sf00357415.1

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

Author: Tim Gardner
Author Date: 2023-04-05 18:19:42 UTC

5.15.0-1037.44~sf00357415.1

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

Author: Tim Gardner
Author Date: 2023-03-01 16:24:07 UTC

5.19.0-1021.22~22.04.2+TEST352899v20230228b1

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: Tim Gardner
Author Date: 2022-12-14 20:09:52 UTC

UBUNTU: Ignore modules

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

Author: Tim Gardner
Author Date: 2022-12-08 15:30:07 UTC

5.15.0-1030.37~lp1999153.1

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

Author: Tim Gardner
Author Date: 2022-11-29 20:08:11 UTC

5.15.0-1025.31~sf00340222.2

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

Author: Tim Gardner
Author Date: 2022-11-15 13:12:49 UTC

5.15.0-1024.30~sf00346757.1

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

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

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: Steve French
Author Date: 2022-07-16 04:57:08 UTC

cifs: remove minor build warning

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

The build warning:
  warning: symbol 'cifs_tcp_ses_lock' was not declared. Should it be static?
can be distracting. Fix two of these.

Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
Signed-off-by: Steve French <stfrench@microsoft.com>
(cherry picked from commit 89e42f49ef58bf5601ce452683aad1cb1088878f)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2022-10-07 16:21:43 UTC

5.15.0-1022.26~lp1991975.1

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

Author: Tim Gardner
Author Date: 2022-09-22 19:11:47 UTC

UBUNTU: Ubuntu-azure-5.15.0-1021.26

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

Author: Tim Gardner
Author Date: 2022-09-21 18:56:36 UTC

UBUNTU: Ubuntu-aws-5.15.0-1021.25

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

Author: Dexuan Cui
Author Date: 2022-08-04 02:51:04 UTC

UBUNTU: SAUCE: PCI: hv: Only reuse existing IRTE allocation for Multi-MSI

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

Jeffrey's 4 recent patches added Multi-MSI support to the pci-hyperv driver.
Unluckily, one of the patches, i.e., b4b77778ecc5, causes a regression to a
fio test for the Azure VM SKU Standard L64s v2 (64 AMD vCPUs, 8 NVMe drives):

when fio runs against all the 8 NVMe drives, it runs fine with a low io-depth
(e.g., 2 or 4); when fio runs with a high io-depth (e.g., 256), somehow
queue-29 of each NVMe drive suddenly no longer receives any interrupts, and
the NVMe core code has to abort the queue after a timeout of 30 seconds, and
then queue-29 starts to receive interrupts again for several seconds, and
later queue-29 no longer receives interrupts again, and this pattern repeats:

[ 223.891249] nvme nvme2: I/O 320 QID 29 timeout, aborting
[ 223.896231] nvme nvme0: I/O 320 QID 29 timeout, aborting
[ 223.898340] nvme nvme4: I/O 832 QID 29 timeout, aborting
[ 259.471309] nvme nvme2: I/O 320 QID 29 timeout, aborting
[ 259.476493] nvme nvme0: I/O 321 QID 29 timeout, aborting
[ 259.482967] nvme nvme0: I/O 322 QID 29 timeout, aborting

Some other symptoms are: the throughput of the NVMe drives drops due to
commit b4b77778ecc5. When the fio test is running, the kernel prints some
soft lock-up messages from time to time.

Commit b4b77778ecc5 itself looks good, and at the moment it's unclear where
the issue is. While the issue is being investigated, restore the old behavior
in hv_compose_msi_msg(), i.e., don't reuse the existing IRTE allocation for
single-MSI and MSI-X. This is a stopgap for the above NVMe issue.

Fixes: b4b77778ecc5 ("PCI: hv: Reuse existing IRTE allocation in compose_msi_msg()")
Signed-off-by: Dexuan Cui <decui@microsoft.com>
Cc: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: Carl Vanderlip <quic_carlv@quicinc.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2022-08-24 18:01:08 UTC

UBUNTU: Ubuntu-azure-fde-5.15.0-1019.24.1

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

Author: Dimitri John Ledkov
Author Date: 2022-08-12 14:46:58 UTC

UBUNTU: Ubuntu-aws-5.15.0-1018.22

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

Author: Tim Gardner
Author Date: 2022-07-22 15:56:56 UTC

5.15.0-46.49~lp1980861.1

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

Author: Dexuan Cui
Author Date: 2022-06-14 20:28:54 UTC

net: mana: Add the Linux MANA PF driver

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

This minimal PF driver runs on bare metal.
Currently Ethernet TX/RX works. SR-IOV management is not supported yet.

Signed-off-by: Dexuan Cui <decui@microsoft.com>
Co-developed-by: Haiyang Zhang <haiyangz@microsoft.com>
Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
(cherry picked from commit 1566e7d6206fed959258a17c694834a4b801a3b5 linux-next)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2022-06-16 17:12:53 UTC

5.15.0-41.44~lp1972662.1

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

Author: Tim Gardner
Author Date: 2022-05-17 17:03:16 UTC

5.15.0-1008.10~lp1970586.1

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

Author: Tim Gardner
Author Date: 2022-05-10 12:45:48 UTC

5.15.0-1006.7~lp1972832.1

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

Author: Tim Gardner
Author Date: 2022-05-09 14:32:40 UTC

5.15.0-1006.7~lp1972662.1

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

Author: Ronnie Sahlberg
Author Date: 2022-04-21 01:15:36 UTC

cifs: destage any unwritten data to the server before calling copychunk_write

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

because the copychunk_write might cover a region of the file that has not yet
been sent to the server and thus fail.

A simple way to reproduce this is:
truncate -s 0 /mnt/testfile; strace -f -o x -ttT xfs_io -i -f -c 'pwrite 0k 128k' -c 'fcollapse 16k 24k' /mnt/testfile

the issue is that the 'pwrite 0k 128k' becomes rearranged on the wire with
the 'fcollapse 16k 24k' due to write-back caching.

fcollapse is implemented in cifs.ko as a SMB2 IOCTL(COPYCHUNK_WRITE) call
and it will fail serverside since the file is still 0b in size serverside
until the writes have been destaged.
To avoid this we must ensure that we destage any unwritten data to the
server before calling COPYCHUNK_WRITE.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1997373
Reported-by: Xiaoli Feng <xifeng@redhat.com>
Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
(cherry picked from commit f5d0f921ea362636e4a2efb7c38d1ead373a8700)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2022-04-27 18:18:39 UTC

5.15.0-1006.7~sf00332721.1

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

Author: Andra Paraschiv
Author Date: 2021-08-27 15:49:30 UTC

nitro_enclaves: Add fixes for checkpatch blank line reports

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

Remove blank lines that are not necessary, fixing the checkpatch script
reports. While at it, add a blank line after the switch default block,
similar to the other parts of the codebase.

Reviewed-by: George-Aurelian Popescu <popegeo@amazon.com>
Signed-off-by: Andra Paraschiv <andraprs@amazon.com>
Link: https://lore.kernel.org/r/20210827154930.40608-8-andraprs@amazon.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit da1c396a81b87541cf7a7c2c6e128b722461a1c8)
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Author: Tim Gardner
Author Date: 2022-01-11 20:31:13 UTC

UBUNTU: Ubuntu-azure-5.15.0-1.1

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

Author: Greg Kroah-Hartman
Author Date: 2022-01-05 11:42:40 UTC

Linux 5.15.13

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

Link: https://lore.kernel.org/r/20220103142056.911344037@linuxfoundation.org
Tested-by: Guenter Roeck <linux@roeck-us.net>
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
Tested-by: Rudi Heitbaum <rudi@heitbaum.com>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Link: https://lore.kernel.org/r/20220104073845.629257314@linuxfoundation.org
Tested-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
Tested-by: Florian Fainelli <f.fainelli@gmail.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
Tested-by: Zan Aziz <zanaziz313@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Paolo Pisati <p.pisati@gmail.com>

Author: Andrea Righi
Author Date: 2021-10-07 09:09:51 UTC

UBUNTU: Ubuntu-5.13.0-19.19

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