lp:~mreed8855/ubuntu/+source/linux/+git/jammy

Author: Chandrakanth Patil
Author Date: 2023-10-03 11:00:20 UTC

scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1

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

Driver version update.

Signed-off-by: Chandrakanth patil <chandrakanth.patil@broadcom.com>
Link: https://lore.kernel.org/r/20231003110021.168862-4-chandrakanth.patil@broadcom.com
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(backported from commit 0938f9fa4208a41a7358eac344fc56b9fd8398dc)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>
[Michael Reed - Simple update to the version and date]

Author: Ranjan Kumar
Author Date: 2023-08-29 09:00:20 UTC

scsi: mpt3sas: Remove volatile qualifier

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

Remove reduntant volatile qualifier.

Signed-off-by: Ranjan Kumar <ranjan.kumar@broadcom.com>
Link: https://lore.kernel.org/r/20230829090020.5417-3-ranjan.kumar@broadcom.com
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 0854065092a7a49a88bb592473abafb0cecd9f1c)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Dan Williams
Author Date: 2022-11-20 01:37:49 UTC

device-dax: Fix duplicate 'hmem' device registration

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

So called "soft-reserved" memory is an EFI conventional memory range
with the EFI_MEMORY_SP attribute set. That attribute indicates that the
memory is not part of the platform general purpose memory pool and may
want some consideration from the system administrator about whether to
keep that memory set aside for dedicated access through device-dax (map
a device file), or assigned to the page allocator as another general
purpose memory node target.

Absent an ACPI HMAT table the default device-dax registration creates
coarse grained devices that are delineated by EFI Memory Map entries.
With the HMAT the devices are delineated by the finer grained ranges
associated with the proximity domain of the memory target. I.e. the HMAT
describes the properties of performance differentiated memory and each
unique performance description results in a unique target proximity
domain where each memory proximity domain has an associated SRAT entry
that delineates the address range.

The intent was that SRAT-defined device-dax instances are registered
first. Then any left-over address range with the EFI_MEMORY_SP
attribute, but not covered by the SRAT, would have a coarse grained
device-dax instance established. However, the scheme to detect what
ranges are left to be assigned to a device was buggy and resulted in
multiple overlapping device-dax instances. Fix this by using explicit
tracking for which ranges have been handled.

Now, this new approach may leave memory stranded in the presence of
broken platform firmware that fails to fully describe all EFI_MEMORY_SP
ranges in the HMAT. That requires a deeper fix if it becomes a problem
in practice.

Reported-by: "Tallam Mahendra Kumar" <tallam.mahendra.kumar@intel.com>
Reported-by: Mustafa Hajeer <mustafa.hajeer@intel.com>
Debugged-by: Vishal Verma <vishal.l.verma@intel.com>
Tested-by: Vishal Verma <vishal.l.verma@intel.com>
Link: https://lore.kernel.org/r/166890823379.4183293.15333502171004313377.stgit@dwillia2-xfh.jf.intel.com
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
(backported from commit 472faf72b33d80aa8e7a99c9410c1a23d3bf0cd8)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>
[Michael Reed - resolved the conflict due to spacing. No changes to the actual patch were made]

Author: Sreekanth Reddy
Author Date: 2021-10-18 07:06:11 UTC

scsi: scsi_transport_sas: Add 22.5 Gbps link rate definitions

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

Add 22.5 Gbps link rate definitions.

Link: https://lore.kernel.org/r/20211018070611.26428-1-sreekanth.reddy@broadcom.com
Reviewed-by: John Garry <john.garry@huawei.com>
Signed-off-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 3d8fa78ebd61aada5d55de6e04beee7fd916c62b)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Sreekanth Reddy
Author Date: 2021-10-18 07:06:11 UTC

scsi: scsi_transport_sas: Add 22.5 Gbps link rate definitions

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

Add 22.5 Gbps link rate definitions.

Link: https://lore.kernel.org/r/20211018070611.26428-1-sreekanth.reddy@broadcom.com
Reviewed-by: John Garry <john.garry@huawei.com>
Signed-off-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 3d8fa78ebd61aada5d55de6e04beee7fd916c62b)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Karan Tilak Kumar
Author Date: 2023-09-19 18:24:36 UTC

scsi: fnic: Fix sg_reset success path

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

sg_reset performs a target or LUN reset. Since the command is issued by the
user, it does not come into the driver with a tag or a queue id. Fix the
fnic driver to create an io_req and use a SCSI command tag. Fix the ITMF
path to special case the sg_reset response.

Reviewed-by: Sesidhar Baddela <sebaddel@cisco.com>
Reviewed-by: Arulprabhu Ponnusamy <arulponn@cisco.com>
Tested-by: Karan Tilak Kumar <kartilak@cisco.com>
Signed-off-by: Karan Tilak Kumar <kartilak@cisco.com>
Link: https://lore.kernel.org/r/20230919182436.6895-1-kartilak@cisco.com
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 514f0c400bde6b62405467daaf2a0a86bcf7794b)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Michael Reed
Author Date: 2023-11-10 07:31:44 UTC

Debugging drivers/scsi/fnic/fnic_scsi.c

Author: Sreekanth Reddy
Author Date: 2021-10-18 07:06:11 UTC

scsi: scsi_transport_sas: Add 22.5 Gbps link rate definitions

https://bugs.launchpad.net/bugs/2029905

Add 22.5 Gbps link rate definitions.

Link: https://lore.kernel.org/r/20211018070611.26428-1-sreekanth.reddy@broadcom.com
Reviewed-by: John Garry <john.garry@huawei.com>
Signed-off-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 3d8fa78ebd61aada5d55de6e04beee7fd916c62b)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Kan Liang
Author Date: 2023-01-12 20:01:01 UTC

perf/x86/uncore: Factor out uncore_device_to_die()

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

The same code is used to retrieve the logical die ID with a given PCI
device in both the discovery code and the code that supports a system
with > 8 nodes.

Factor out uncore_device_to_die() to replace the duplicate code.

No functional change.

Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Tested-by: Michael Petlan <mpetlan@redhat.com>
Link: https://lore.kernel.org/r/20230112200105.733466-2-kan.liang@linux.intel.com
(cherry picked from commit dbf061b26221fa1a99e6489dd61f5b4ee97a24e8)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Sagi Grimberg
Author Date: 2022-11-29 14:43:19 UTC

nvme-multipath: support io stats on the mpath device

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

Our mpath stack device is just a shim that selects a bottom namespace
and submits the bio to it without any fancy splitting. This also means
that we don't clone the bio or have any context to the bio beyond
submission. However it really sucks that we don't see the mpath device
io stats.

Given that the mpath device can't do that without adding some context
to it, we let the bottom device do it on its behalf (somewhat similar
to the approach taken in nvme_trace_bio_complete).

When the IO starts, we account the request for multipath IO stats using
REQ_NVME_MPATH_IO_STATS nvme_request flag to avoid queue io stats disable
in the middle of the request.

Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Keith Busch <kbusch@kernel.org>
(backported from commit d4d957b53d91eebc8c681c480edfdc697e55231e)
[Michael Reed - Adjusted location of code from patch]
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Michael Reed
Author Date: 2023-09-07 20:30:23 UTC

UBUNTU: [Config] CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE

BugLink: https://bugs.launchpad.net/bugs/2028158
By default this is enabled, but it is causing an issue reconfiguring device dax memory, thus
it is being disabled.

Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Srinivas Pandruvada
Author Date: 2023-06-29 19:45:09 UTC

cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled E-cores

https://bugs.launchpad.net/bugs/2030924

Some system BIOS configuration may provide option to disable E-cores.
As part of this change, CPUID feature for hybrid (Leaf 7 sub leaf 0,
EDX[15] = 0) may not be set. But HWP performance limits will still be
using a scaling factor like any other hybrid enabled system.

The current check for applying scaling factor will fail when hybrid
CPUID feature is not set and the only way to make sure that scaling
should be applied by checking CPPC nominal frequency and nominal
performance.

First, or systems predating Alder Lake, the CPPC nominal frequency and
nominal performance are 0, which can be used to distinguish those
systems from hybrid systems with disabled E-cores.

Second, if the CPPC nominal frequency and nominal performance are
defined, which indicates the need to use a special scaling factor, and
the nominal performance value multiplied by 100 is not equal to the
nominal frequency one, use hybrid scaling factor.

This can be done for all HWP systems without additional CPU model check.

Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
[ rjw: Subject and changelog edits, removal of unneeded parens, comment
  edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit 0fcfc9e51990246a9813475716746ff5eb98c6aa)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Dimitri John Ledkov
Author Date: 2023-07-27 16:31:00 UTC

UBUNTU: [Config] Enable FW_LOADER_COMPRESS_ZSTD by default

This is to aid upgrade to releases that require support for zstd
compressed firmware.

BugLink: https://bugs.launchpad.net/bugs/2028550
Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Acked-by: Roxana Nicolescu <roxana.nicolescu@canonical.com>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>

Author: Michael Reed
Author Date: 2023-07-18 16:39:08 UTC

UBUNTU: SAUCE:

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

Resolve conflicts due to reverted patches.

Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq"
Revert "scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4"
Revert "scsi: lpfc: SLI path split: Refactor SCSI paths"
Revert "scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup()"
Revert "scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()"
Revert "scsi: lpfc: Resolve some cleanup issues following SLI path refactoring"

The patch set applied to update the lpfc driver was based on the kernel
before the reverted patches were applied. This patch resolves the issues
in the driver caused by the reverted patches.

<Why is this patch not going upstream?>

Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: James Smart
Author Date: 2022-04-12 22:20:08 UTC

scsi: lpfc: Copyright updates for 14.2.0.2 patches

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

Update copyrights to 2022 for files modified in the 14.2.0.2 patch set.

Link: https://lore.kernel.org/r/20220412222008.126521-27-jsmart2021@gmail.com
Co-developed-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 66c20a97367a6a9254af7cf863271d55a731a4a0)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: James Smart
Author Date: 2022-10-28 21:08:27 UTC

Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq"

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

This reverts commit 1c5e670d6a5a8e7e99b51f45e79879f7828bd2ec.

LTS 5.15 pulled in several lpfc "SLI Path split" patches. The Path
Split mods were a 14-patch set, which refactors the driver from
to split the sli-3 hw (now eol) from the sli-4 hw and use sli4
structures natively. The patches are highly inter-related.

Given only some of the patches were included, it created a situation
where FLOGI's fail, thus SLI Ports can't start communication.

Reverting this patch as its one of the partial Path Split patches
that was included.

Signed-off-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(backported from commit 0b0d169723f41bee4586384430f13435cb35b979)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>
[Michael Reed - Reverted instances of struct member cmd_cmpl to iocb_cmpl]

Author: Michael Reed
Author Date: 2023-06-14 16:21:56 UTC

UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

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

Currently Ubuntu kernel has this kernel config disabled.
But in some cases, Intel's Sapphire Rapids High Bandwith
Memory (SPR-HBM) needs this option.

Memory bandwidth has been a bottleneck of increasingly memory bound
workloads. Sapphire Rapids plus HBM is specifically targeted to
cater to these workloads, traditionally served using overprovisioning
of memory devices.

Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: James Smart
Author Date: 2022-07-01 21:14:25 UTC

scsi: lpfc: Copyright updates for 14.2.0.5 patches

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

Update copyrights to 2022 for files modified in the 14.2.0.5 patch set.

Link: https://lore.kernel.org/r/20220701211425.2708-13-jsmart2021@gmail.com
Co-developed-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit b3d11f195cbbe665c100b964f6837984b4226cd1)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: James Smart
Author Date: 2022-07-01 21:14:25 UTC

scsi: lpfc: Copyright updates for 14.2.0.5 patches

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

Update copyrights to 2022 for files modified in the 14.2.0.5 patch set.

Link: https://lore.kernel.org/r/20220701211425.2708-13-jsmart2021@gmail.com
Co-developed-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit b3d11f195cbbe665c100b964f6837984b4226cd1)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Don Brace
Author Date: 2022-11-08 19:22:14 UTC

scsi: smartpqi: Change version to 2.1.20-035

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

Reviewed-by: Scott Benesh <scott.benesh@microchip.com>
Reviewed-by: Scott Teel <scott.teel@microchip.com>
Reviewed-by: Gerry Morong <gerry.morong@microchip.com>
Reviewed-by: Kevin Barnett <kevin.barnett@microchip.com>
Signed-off-by: Don Brace <don.brace@microchip.com>
Link: https://lore.kernel.org/r/166793533417.322537.3074216622272955440.stgit@brunhilda
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 2ae45329a956ff86ff8bec36463b6f49d2ca9bea)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Don Brace
Author Date: 2022-11-08 19:22:14 UTC

scsi: smartpqi: Change version to 2.1.20-035

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

Reviewed-by: Scott Benesh <scott.benesh@microchip.com>
Reviewed-by: Scott Teel <scott.teel@microchip.com>
Reviewed-by: Gerry Morong <gerry.morong@microchip.com>
Reviewed-by: Kevin Barnett <kevin.barnett@microchip.com>
Signed-off-by: Don Brace <don.brace@microchip.com>
Link: https://lore.kernel.org/r/166793533417.322537.3074216622272955440.stgit@brunhilda
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 2ae45329a956ff86ff8bec36463b6f49d2ca9bea)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Don Brace
Author Date: 2022-11-08 19:22:14 UTC

scsi: smartpqi: Change version to 2.1.20-035

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

Reviewed-by: Scott Benesh <scott.benesh@microchip.com>
Reviewed-by: Scott Teel <scott.teel@microchip.com>
Reviewed-by: Gerry Morong <gerry.morong@microchip.com>
Reviewed-by: Kevin Barnett <kevin.barnett@microchip.com>
Signed-off-by: Don Brace <don.brace@microchip.com>
Link: https://lore.kernel.org/r/166793533417.322537.3074216622272955440.stgit@brunhilda
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 2ae45329a956ff86ff8bec36463b6f49d2ca9bea)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Don Brace
Author Date: 2022-11-08 19:22:14 UTC

scsi: smartpqi: Change version to 2.1.20-035

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

Reviewed-by: Scott Benesh <scott.benesh@microchip.com>
Reviewed-by: Scott Teel <scott.teel@microchip.com>
Reviewed-by: Gerry Morong <gerry.morong@microchip.com>
Reviewed-by: Kevin Barnett <kevin.barnett@microchip.com>
Signed-off-by: Don Brace <don.brace@microchip.com>
Link: https://lore.kernel.org/r/166793533417.322537.3074216622272955440.stgit@brunhilda
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 2ae45329a956ff86ff8bec36463b6f49d2ca9bea)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Jerry Hoemann
Author Date: 2022-08-20 20:28:20 UTC

watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING

Fixes: d48b0e173715 ("x86, nmi, drivers: Fix nmi splitup build bug")

Arm64 does not support NMI and has no <asm/nmi.h>.

Include <asm/nmi.h> only if CONFIG_HPWDT_NMI_DECODING is defined to
avoid build failure on non-existent header file on Arm64.

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

Signed-off-by: Jerry Hoemann <jerry.hoemann@hpe.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/r/20220820202821.1263837-2-jerry.hoemann@hpe.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
(cherry picked from commit ed835d8171fc884c7750cdd54128df16d4571e3a)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Michael Reed
Author Date: 2023-03-02 20:54:11 UTC

UBUNTU: [Config] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

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

Currently Ubuntu kernel has this kernel config disabled.
But in some cases, Intel's Sapphire Rapids High Bandwith
Memory (SPR-HBM) needs this option.

Memory bandwidth has been a bottleneck of increasingly memory bound
workloads. Sapphire Rapids plus HBM is specifically targeted to
cater to these workloads, traditionally served using overprovisioning
of memory devices.

Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Jerry Hoemann
Author Date: 2022-08-20 20:28:20 UTC

watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING

Fixes: d48b0e173715 ("x86, nmi, drivers: Fix nmi splitup build bug")

Arm64 does not support NMI and has no <asm/nmi.h>.

Include <asm/nmi.h> only if CONFIG_HPWDT_NMI_DECODING is defined to
avoid build failure on non-existent header file on Arm64.

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

Signed-off-by: Jerry Hoemann <jerry.hoemann@hpe.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/r/20220820202821.1263837-2-jerry.hoemann@hpe.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
(cherry picked from commit ed835d8171fc884c7750cdd54128df16d4571e3a)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Stuart Hayes
Author Date: 2022-11-02 19:59:57 UTC

cpufreq: ACPI: Defer setting boost MSRs

When acpi-cpufreq is loaded, boost is enabled on every CPU (by setting an
MSR) before the driver is registered with cpufreq. This can be very time
consuming, because it is done with a CPU hotplug startup callback, and
cpuhp_setup_state() schedules the callback (cpufreq_boost_online()) to run
on each CPU one at a time, waiting for each to run before calling the next.

If cpufreq_register_driver() fails--if, for example, there are no ACPI
P-states present--this is wasted time.

Since cpufreq already sets up a CPU hotplug startup callback if and when
acpi-cpufreq is registered, set the boost MSRs in acpi_cpufreq_cpu_init(),
which is called by the cpufreq cpuhp callback. This allows acpi-cpufreq to
exit quickly if it is loaded but not needed.

On one system with 192 CPUs, this patch speeds up boot by about 30 seconds.

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

Signed-off-by: Stuart Hayes <stuart.w.hayes@gmail.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit 13fdbc8b8da6a2325cad3359c9a70504b0ff2f93)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Gustavo A. R. Silva
Author Date: 2022-08-15 21:52:33 UTC

scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC

Prefer struct_size() over open-coded versions of idiom:

        sizeof(struct-with-flex-array) + sizeof(type-of-flex-array) * count

where count is the max number of items the flexible array is supposed to
have.

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

Link: https://github.com/KSPP/linux/issues/160
Link: https://lore.kernel.org/r/b215f4760f0e8fbe5fc35be20f2487e89924424d.1660592640.git.gustavoars@kernel.org
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 48658213202c4f48ef34b43b9b6f60af8b67fb8a)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Jiapeng Chong
Author Date: 2022-05-25 09:35:14 UTC

scsi: mpi3mr: Fix kernel-doc

Fix the following W=1 kernel warnings:

drivers/scsi/mpi3mr/mpi3mr_app.c:1706: warning: expecting prototype for
adapter_state_show(). Prototype was for adp_state_show() instead.

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

Link: https://lore.kernel.org/r/20220525093514.55467-1-jiapeng.chong@linux.alibaba.com
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 1fcbe4c490396c5a0d4588cfb84923ad6076b62a)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Michael Reed
Author Date: 2022-08-12 22:23:27 UTC

UBUNTU: SAUCE: (no-up) mpi3mr -- Adjustments had to be made for two patches to build.

mpi3mr: Add management application interface(BSG) support

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

The first patch "256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR"
introduces the issue with scsi_done(scmd) where it should be scmd->scsi_done(scmd);

The second patch "986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs"
adds this line .shost_groups = mpi3mr_host_groups and has to be removed

Author: Stuart Hayes
Author Date: 2022-11-02 19:59:57 UTC

cpufreq: ACPI: Defer setting boost MSRs

When acpi-cpufreq is loaded, boost is enabled on every CPU (by setting an
MSR) before the driver is registered with cpufreq. This can be very time
consuming, because it is done with a CPU hotplug startup callback, and
cpuhp_setup_state() schedules the callback (cpufreq_boost_online()) to run
on each CPU one at a time, waiting for each to run before calling the next.

If cpufreq_register_driver() fails--if, for example, there are no ACPI
P-states present--this is wasted time.

Since cpufreq already sets up a CPU hotplug startup callback if and when
acpi-cpufreq is registered, set the boost MSRs in acpi_cpufreq_cpu_init(),
which is called by the cpufreq cpuhp callback. This allows acpi-cpufreq to
exit quickly if it is loaded but not needed.

On one system with 192 CPUs, this patch speeds up boot by about 30 seconds.

Signed-off-by: Stuart Hayes <stuart.w.hayes@gmail.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit 13fdbc8b8da6a2325cad3359c9a70504b0ff2f93)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

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

Author: Gustavo A. R. Silva
Author Date: 2022-08-15 21:52:33 UTC

scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC

Prefer struct_size() over open-coded versions of idiom:

        sizeof(struct-with-flex-array) + sizeof(type-of-flex-array) * count

where count is the max number of items the flexible array is supposed to
have.

Link: https://github.com/KSPP/linux/issues/160
Link: https://lore.kernel.org/r/b215f4760f0e8fbe5fc35be20f2487e89924424d.1660592640.git.gustavoars@kernel.org
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 48658213202c4f48ef34b43b9b6f60af8b67fb8a)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

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

Author: Jerry Hoemann
Author Date: 2022-08-20 20:28:20 UTC

watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING

Fixes: d48b0e173715 ("x86, nmi, drivers: Fix nmi splitup build bug")

Arm64 does not support NMI and has no <asm/nmi.h>.

Include <asm/nmi.h> only if CONFIG_HPWDT_NMI_DECODING is defined to
avoid build failure on non-existent header file on Arm64.

Signed-off-by: Jerry Hoemann <jerry.hoemann@hpe.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/r/20220820202821.1263837-2-jerry.hoemann@hpe.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
(cherry picked from commit ed835d8171fc884c7750cdd54128df16d4571e3a)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

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

Author: BruceAllan
Author Date: 2020-02-13 21:31:28 UTC

ice: add support for E823 devices

Add E823 device ids and convert conditional expressions to a more
appropriate switch statement.

Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
(cherry picked from commit e36aeec0f4e551a7fe01758e652d135638b4865b)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

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

Author: Stefan Bader
Author Date: 2022-10-13 07:40:20 UTC

UBUNTU: Ubuntu-5.15.0-52.58

Signed-off-by: Stefan Bader <stefan.bader@canonical.com>

Author: Daniel Wagner
Author Date: 2022-08-29 09:28:39 UTC

nvmet: expose max queues to configfs

Allow to set the max queues the target supports. This is useful for
testing the reconnect attempt of the host with changing numbers of
supported queues.

Signed-off-by: Daniel Wagner <dwagner@suse.de>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
(cherry picked from commit 3e980f5995e0bb4d86fef873a9c9ad66721580d0)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

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

Author: Brett Creeley
Author Date: 2021-05-05 21:17:57 UTC

ice: Remove toggling of antispoof for VF trusted promiscuous mode

Currently when a trusted VF enables promiscuous mode spoofchk will be
disabled. This is wrong and should only be modified from the
ndo_set_vf_spoofchk callback. Fix this by removing the call to toggle
spoofchk for trusted VFs.

Fixes: 01b5e89aab49 ("ice: Add VF promiscuous support")
Signed-off-by: Brett Creeley <brett.creeley@intel.com>
Tested-by: Tony Brelinski <tony.brelinski@intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
(cherry picked from commit 0299faeaf8eb982103e4388af61fd94feb9c2d9f)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

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

Author: Suganath Prabu
Author Date: 2021-12-27 05:30:55 UTC

scsi: mpt3sas: Update persistent trigger pages from sysfs interface

Store sysfs-provided trigger values into the corresponding persistent
trigger pages. Otherwise trigger entries are not persistent across system
reboots.

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

Link: https://lore.kernel.org/r/20211227053055.289537-1-suganath-prabu.subramani@broadcom.com
Signed-off-by: Suganath Prabu S <suganath-prabu.subramani@broadcom.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 9211faa39a0350fb2239a0bce03b9459cd14fc40)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Michael Reed
Author Date: 2022-08-12 22:23:27 UTC

mpi3mr: Add management application interface(BSG) support

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

Adjustments had to be made for two patches.

The first patch "256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR"
introduces the issue with scsi_done(scmd) where it should be scmd->scsi_done(scmd);

The second patch "986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs"
adds this line .shost_groups = mpi3mr_host_groups and has to be removed

Author: Jiapeng Chong
Author Date: 2022-05-25 09:35:14 UTC

scsi: mpi3mr: Fix kernel-doc

Fix the following W=1 kernel warnings:

drivers/scsi/mpi3mr/mpi3mr_app.c:1706: warning: expecting prototype for
adapter_state_show(). Prototype was for adp_state_show() instead.

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

Link: https://lore.kernel.org/r/20220525093514.55467-1-jiapeng.chong@linux.alibaba.com
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit 1fcbe4c490396c5a0d4588cfb84923ad6076b62a)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Kleber Sacilotto de Souza
Author Date: 2022-05-31 16:39:02 UTC

UBUNTU: Ubuntu-5.15.0-36.37

Signed-off-by: Kleber Sacilotto de Souza <kleber.souza@canonical.com>

Author: Michael Reed
Author Date: 2022-05-17 20:21:08 UTC

Enable config option CONFIG_PCIE_EDR
BugLink: https://bugs.launchpad.net/bugs/1965241

Author: Sumit Saxena
Author Date: 2022-04-29 21:16:41 UTC

scsi: mpi3mr: Update driver version to 8.0.0.69.0

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

Link: https://lore.kernel.org/r/20220429211641.642010-9-sumit.saxena@broadcom.com
Signed-off-by: Sumit Saxena <sumit.saxena@broadcom.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit f304d35e59958ea4be399f78e5be08d4a0c4db75)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Martin Belanger
Author Date: 2022-02-08 19:33:46 UTC

nvme: expose cntrltype and dctype through sysfs

TP8010 introduces the Discovery Controller Type attribute (dctype).
The dctype is returned in the response to the Identify command. This
patch exposes the dctype through the sysfs. Since the dctype depends on
the Controller Type (cntrltype), another attribute of the Identify
response, the patch also exposes the cntrltype as well. The dctype will
only be displayed for discovery controllers.

A note about the naming of this attribute:
Although TP8010 calls this attribute the Discovery Controller Type,
note that the dctype is now part of the response to the Identify
command for all controller types. I/O, Discovery, and Admin controllers
all share the same Identify response PDU structure. Non-discovery
controllers as well as pre-TP8010 discovery controllers will continue
to set this field to 0 (which has always been the default for reserved
bytes). Per TP8010, the value 0 now means "Discovery controller type is
not reported" instead of "Reserved". One could argue that this
definition is correct even for non-discovery controllers, and by
extension, exposing it in the sysfs for non-discovery controllers is
appropriate.

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

Signed-off-by: Martin Belanger <martin.belanger@dell.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: John Meneghini <jmeneghi@redhat.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
(cherry picked from commit 86c2457a8e8112f16af8fd10a3e1dd7a302c3c3e linux-next)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Martin Belanger
Author Date: 2022-02-08 19:33:46 UTC

nvme: expose cntrltype and dctype through sysfs

TP8010 introduces the Discovery Controller Type attribute (dctype).
The dctype is returned in the response to the Identify command. This
patch exposes the dctype through the sysfs. Since the dctype depends on
the Controller Type (cntrltype), another attribute of the Identify
response, the patch also exposes the cntrltype as well. The dctype will
only be displayed for discovery controllers.

A note about the naming of this attribute:
Although TP8010 calls this attribute the Discovery Controller Type,
note that the dctype is now part of the response to the Identify
command for all controller types. I/O, Discovery, and Admin controllers
all share the same Identify response PDU structure. Non-discovery
controllers as well as pre-TP8010 discovery controllers will continue
to set this field to 0 (which has always been the default for reserved
bytes). Per TP8010, the value 0 now means "Discovery controller type is
not reported" instead of "Reserved". One could argue that this
definition is correct even for non-discovery controllers, and by
extension, exposing it in the sysfs for non-discovery controllers is
appropriate.

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

Signed-off-by: Martin Belanger <martin.belanger@dell.com>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: John Meneghini <jmeneghi@redhat.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
(cherry picked from commit 86c2457a8e8112f16af8fd10a3e1dd7a302c3c3e linux-next)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>

Author: Lukas Wunner
Author Date: 2021-07-31 12:39:01 UTC

PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset

Stuart Hayes reports that an error handled by DPC at a Root Port results
in pciehp gratuitously bringing down a subordinate hotplug port:

  RP -- UP -- DP -- UP -- DP (hotplug) -- EP

pciehp brings the slot down because the Link to the Endpoint goes down.
That is caused by a Hot Reset being propagated as a result of DPC.
Per PCIe Base Spec 5.0, section 6.6.1 "Conventional Reset":

  For a Switch, the following must cause a hot reset to be sent on all
  Downstream Ports: [...]

  * The Data Link Layer of the Upstream Port reporting DL_Down status.
    In Switches that support Link speeds greater than 5.0 GT/s, the
    Upstream Port must direct the LTSSM of each Downstream Port to the
    Hot Reset state, but not hold the LTSSMs in that state. This permits
    each Downstream Port to begin Link training immediately after its
    hot reset completes. This behavior is recommended for all Switches.

  * Receiving a hot reset on the Upstream Port.

Once DPC recovers, pcie_do_recovery() walks down the hierarchy and
invokes pcie_portdrv_slot_reset() to restore each port's config space.
At that point, a hotplug interrupt is signaled per PCIe Base Spec r5.0,
section 6.7.3.4 "Software Notification of Hot-Plug Events":

  If the Port is enabled for edge-triggered interrupt signaling using
  MSI or MSI-X, an interrupt message must be sent every time the logical
  AND of the following conditions transitions from FALSE to TRUE: [...]

  * The Hot-Plug Interrupt Enable bit in the Slot Control register is
    set to 1b.

  * At least one hot-plug event status bit in the Slot Status register
    and its associated enable bit in the Slot Control register are both
    set to 1b.

Prevent pciehp from gratuitously bringing down the slot by clearing the
error-induced Data Link Layer State Changed event before restoring
config space. Afterwards, check whether the link has unexpectedly
failed to retrain and synthesize a DLLSC event if so.

Allow each pcie_port_service_driver (one of them being pciehp) to define
a slot_reset callback and re-use the existing pm_iter() function to
iterate over the callbacks.

Thereby, the Endpoint driver remains bound throughout error recovery and
may restore the device to working state.

Surprise removal during error recovery is detected through a Presence
Detect Changed event. The hotplug port is expected to not signal that
event as a result of a Hot Reset.

The issue isn't DPC-specific, it also occurs when an error is handled by
AER through aer_root_reset(). So while the issue was noticed only now,
it's been around since 2006 when AER support was first introduced.

[bhelgaas: drop PCI_ERROR_RECOVERY Kconfig, split pm_iter() rename to
preparatory patch]

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

Link: https://lore.kernel.org/linux-pci/08c046b0-c9f2-3489-eeef-7e7aca435bb9@gmail.com/
Fixes: 6c2b374d7485 ("PCI-Express AER implemetation: AER core and aerdriver")
Link: https://lore.kernel.org/r/251f4edcc04c14f873ff1c967bc686169cd07d2d.1627638184.git.lukas@wunner.de
Reported-by: Stuart Hayes <stuart.w.hayes@gmail.com>
Tested-by: Stuart Hayes <stuart.w.hayes@gmail.com>
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Cc: stable@vger.kernel.org # v2.6.19+: ba952824e6c1: PCI/portdrv: Report reset for frozen channel
Cc: Keith Busch <kbusch@kernel.org>
(cherry picked from commit ea401499e943c307e6d44af6c2b4e068643e7884 linus)
Signed-off-by: Michael Reed <Michael.Reed@canonical.com>