Linux 6.5.11

 
ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection [+ + +]
Author: Mark Hasemeyer <markhas@chromium.org>
Date:   Wed Oct 18 17:59:31 2023 -0600

    ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection
    
    commit 7c05b44e1a50d9cbfc4f731dddc436a24ddc129a upstream.
    
    Some Jasperlake Chromebooks overwrite the system vendor DMI value to the
    name of the OEM that manufactured the device. This breaks Chromebook
    quirk detection as it expects the system vendor to be "Google".
    
    Add another quirk detection entry that looks for "Google" in the BIOS
    version.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
    Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Link: https://lore.kernel.org/r/20231018235944.1860717-1-markhas@chromium.org
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

ALSA: usb-audio: add quirk flag to enable native DSD for McIntosh devices [+ + +]
Author: Max McCarthy <mmccarthy@mcintoshlabs.com>
Date:   Tue Oct 24 12:30:19 2023 +0000

    ALSA: usb-audio: add quirk flag to enable native DSD for McIntosh devices
    
    commit 99248c8902f505ec064cf2b0f74629016f2f4c82 upstream.
    
    McIntosh devices supporting native DSD require the feature to be
    explicitly exposed. Add a flag that fixes an issue where DSD audio was
    defaulting to DSD over PCM instead of delivering raw DSD data.
    
    Signed-off-by: Max McCarthy <mmccarthy@mcintoshlabs.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/BL0PR13MB4433226005162D186A8DFF4AD6DFA@BL0PR13MB4433.namprd13.prod.outlook.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
arm64: dts: imx93: add the Flex-CAN stop mode by GPR [+ + +]
Author: Haibo Chen <haibo.chen@nxp.com>
Date:   Wed Jul 26 19:24:57 2023 +0800

    arm64: dts: imx93: add the Flex-CAN stop mode by GPR
    
    [ Upstream commit 23ed2be5404da7cee6a519fa69bf22d0f69da4e4 ]
    
    imx93 A0 chip use the internal q-channel handshake signal in LPCG
    and CCM to automatically handle the Flex-CAN stop mode. But this
    method meet issue when do the system PM stress test. IC can't fix
    it easily. So in the new imx93 A1 chip, IC drop this method, and
    involve back the old way,use the GPR method to trigger the Flex-CAN
    stop mode signal. Now NXP claim to drop imx93 A0, and only support
    imx93 A1. So here add the stop mode through GPR.
    
    This patch also fix a typo for aonmix_ns_gpr.
    
    Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
    Link: https://lore.kernel.org/all/20230726112458.3524165-1-haibo.chen@nxp.com
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
ASoC: codecs: tas2780: Fix log of failed reset via I2C. [+ + +]
Author: Roy Chateau <roy.chateau@mep-info.com>
Date:   Fri Oct 13 13:02:39 2023 +0200

    ASoC: codecs: tas2780: Fix log of failed reset via I2C.
    
    [ Upstream commit 4e9a429ae80657bdc502d3f5078e2073656ec5fd ]
    
    Correctly log failures of reset via I2C.
    
    Signed-off-by: Roy Chateau <roy.chateau@mep-info.com>
    Link: https://lore.kernel.org/r/20231013110239.473123-1-roy.chateau@mep-info.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: core: Do not call link_exit() on uninitialized rtd objects [+ + +]
Author: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
Date:   Fri Sep 29 12:32:43 2023 +0200

    ASoC: core: Do not call link_exit() on uninitialized rtd objects
    
    [ Upstream commit dd9f9cc1e6b9391140afa5cf27bb47c9e2a08d02 ]
    
    On init we have sequence:
    
            for_each_card_prelinks(card, i, dai_link) {
                    ret = snd_soc_add_pcm_runtime(card, dai_link);
    
            ret = init_some_other_things(...);
            if (ret)
                    goto probe_end:
    
            for_each_card_rtds(card, rtd) {
                    ret = soc_init_pcm_runtime(card, rtd);
    
    probe_end:
    
    while on exit:
            for_each_card_rtds(card, rtd)
                    snd_soc_link_exit(rtd);
    
    If init_some_other_things() step fails due to error we end up with
    not fully setup rtds and try to call snd_soc_link_exit on them, which
    depending on contents on .link_exit handler, can end up dereferencing
    NULL pointer.
    
    Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
    Signed-off-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
    Link: https://lore.kernel.org/r/20230929103243.705433-2-amadeuszx.slawinski@linux.intel.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: da7219: Correct the process of setting up Gnd switch in AAD [+ + +]
Author: David Rau <David.Rau.opensource@dm.renesas.com>
Date:   Tue Oct 17 10:12:58 2023 +0800

    ASoC: da7219: Correct the process of setting up Gnd switch in AAD
    
    [ Upstream commit e8ecffd9962fe051d53a0761921b26d653b3df6b ]
    
    Enable Gnd switch to improve stability when Jack insert event
    occurs, and then disable Gnd switch after Jack type detection
    is finished.
    
    Signed-off-by: David Rau <David.Rau.opensource@dm.renesas.com>
    Link: https://lore.kernel.org/r/20231017021258.5929-1-David.Rau.opensource@dm.renesas.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: fsl-asoc-card: use integer type for fll_id and pll_id [+ + +]
Author: Shengjiu Wang <shengjiu.wang@nxp.com>
Date:   Wed Sep 20 17:43:12 2023 +0800

    ASoC: fsl-asoc-card: use integer type for fll_id and pll_id
    
    [ Upstream commit 2b21207afd06714986a3d22442ed4860ba4f9ced ]
    
    As the pll_id and pll_id can be zero (WM8960_SYSCLK_AUTO)
    with the commit 2bbc2df46e67 ("ASoC: wm8960: Make automatic the
    default clocking mode")
    
    Then the machine driver will skip to call set_sysclk() and set_pll()
    for codec, when the sysclk rate is different with what wm8960 read
    at probe, the output sound frequency is wrong.
    
    So change the fll_id and pll_id initial value, still keep machine
    driver's behavior same as before.
    
    Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
    Link: https://lore.kernel.org/r/1695202992-24864-1-git-send-email-shengjiu.wang@nxp.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: Intel: sof_sdw: add support for SKU 0B14 [+ + +]
Author: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Date:   Tue Sep 19 17:21:25 2023 +0800

    ASoC: Intel: sof_sdw: add support for SKU 0B14
    
    [ Upstream commit fb0b8d299781be8d46b3612aa96cef28da0d93f4 ]
    
    One more missing SKU in the list.
    
    Closes: https://github.com/thesofproject/linux/issues/4543
    Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Reviewed-by: Chao Song <chao.song@linux.intel.com>
    Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
    Link: https://lore.kernel.org/r/20230919092125.1922468-1-yung-chuan.liao@linux.intel.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
ASoC: rt5650: fix the wrong result of key button [+ + +]
Author: Shuming Fan <shumingf@realtek.com>
Date:   Fri Oct 13 17:45:25 2023 +0800

    ASoC: rt5650: fix the wrong result of key button
    
    [ Upstream commit f88dfbf333b3661faff996bb03af2024d907b76a ]
    
    The RT5650 should enable a power setting for button detection to avoid the wrong result.
    
    Signed-off-by: Shuming Fan <shumingf@realtek.com>
    Link: https://lore.kernel.org/r/20231013094525.715518-1-shumingf@realtek.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: simple-card: fixup asoc_simple_probe() error handling [+ + +]
Author: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Date:   Tue Sep 19 05:34:18 2023 +0000

    ASoC: simple-card: fixup asoc_simple_probe() error handling
    
    [ Upstream commit 41bae58df411f9accf01ea660730649b2fab1dab ]
    
    asoc_simple_probe() is used for both "DT probe" (A) and "platform probe"
    (B). It uses "goto err" when error case, but it is not needed for
    "platform probe" case (B). Thus it is using "return" directly there.
    
            static int asoc_simple_probe(...)
            {
     ^              if (...) {
     |                      ...
    (A)                     if (ret < 0)
     |                              goto err;
     v              } else {
     ^                      ...
     |                      if (ret < 0)
    (B)                             return -Exxx;
     v              }
    
                    ...
     ^              if (ret < 0)
    (C)                     goto err;
     v              ...
    
            err:
    (D)             simple_util_clean_reference(card);
    
                    return ret;
            }
    
    Both case are using (C) part, and it calls (D) when err case.
    But (D) will do nothing for (B) case.
    Because of these behavior, current code itself is not wrong,
    but is confusable, and more, static analyzing tool will warning on
    (B) part (should use goto err).
    
    To avoid static analyzing tool warning, this patch uses "goto err"
    on (B) part.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
    Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
    Link: https://lore.kernel.org/r/87o7hy7mlh.wl-kuninori.morimoto.gx@renesas.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: soc-dapm: Add helper for comparing widget name [+ + +]
Author: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Date:   Tue Oct 3 17:57:09 2023 +0200

    ASoC: soc-dapm: Add helper for comparing widget name
    
    [ Upstream commit 76aca10ccb7c23a7b7a0d56e0bfde2c8cdddfe24 ]
    
    Some drivers use one event callback for multiple widgets but still need
    to perform a bit different actions based on actual widget.  This is done
    by comparing widget name, however drivers tend to miss possible name
    prefix.  Add a helper to solve common mistakes.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
    Link: https://lore.kernel.org/r/20231003155710.821315-2-krzysztof.kozlowski@linaro.org
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ASoC: SOF: sof-pci-dev: Fix community key quirk detection [+ + +]
Author: Mark Hasemeyer <markhas@chromium.org>
Date:   Fri Oct 20 14:59:53 2023 -0600

    ASoC: SOF: sof-pci-dev: Fix community key quirk detection
    
    commit 7dd692217b861a8292ff8ac2c9d4458538fd6b96 upstream.
    
    Some Chromebooks do not populate the product family DMI value resulting
    in firmware load failures.
    
    Add another quirk detection entry that looks for "Google" in the BIOS
    version. Theoretically, PRODUCT_FAMILY could be replaced with
    BIOS_VERSION, but it is left as a quirk to be conservative.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Mark Hasemeyer <markhas@chromium.org>
    Acked-by: Curtis Malainey <cujomalainey@chromium.org>
    Link: https://lore.kernel.org/r/20231020145953.v1.1.Iaf5702dc3f8af0fd2f81a22ba2da1a5e15b3604c@changeid
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

ASoC: tlv320adc3xxx: BUG: Correct micbias setting [+ + +]
Author: Antoine Gennart <gennartan@disroot.org>
Date:   Fri Sep 29 15:01:17 2023 +0200

    ASoC: tlv320adc3xxx: BUG: Correct micbias setting
    
    [ Upstream commit e930bea4124b8a4a47ba4092d99da30099b9242d ]
    
    The micbias setting for tlv320adc can also have the value '3' which
    means that the micbias ouput pin is connected to the input pin AVDD.
    
    Signed-off-by: Antoine Gennart <gennartan@disroot.org>
    Link: https://lore.kernel.org/r/20230929130117.77661-1-gennartan@disroot.org
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
ata: pata_parport: add custom version of wait_after_reset [+ + +]
Author: Ondrej Zary <linux@zary.sk>
Date:   Thu Oct 5 22:55:58 2023 +0200

    ata: pata_parport: add custom version of wait_after_reset
    
    [ Upstream commit f343e578fef99a69b3322aca38b94a6d8ded2ce7 ]
    
    Some parallel adapters (e.g. EXP Computer MC-1285B EPP Cable) return
    bogus values when there's no master device present. This can cause
    reset to fail, preventing the lone slave device (such as EXP Computer
    CD-865) from working.
    
    Add custom version of wait_after_reset that ignores master failure when
    a slave device is present. The custom version is also needed because
    the generic ata_sff_wait_after_reset uses direct port I/O for slave
    device detection.
    
    Signed-off-by: Ondrej Zary <linux@zary.sk>
    Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

ata: pata_parport: fit3: implement IDE command set registers [+ + +]
Author: Ondrej Zary <linux@zary.sk>
Date:   Thu Oct 5 22:55:59 2023 +0200

    ata: pata_parport: fit3: implement IDE command set registers
    
    [ Upstream commit 0c1e81d0b5ebd5813536dd5fcf5966ad043f37dc ]
    
    fit3 protocol driver does not support accessing IDE control registers
    (device control/altstatus). The DOS driver does not use these registers
    either (as observed from DOSEMU trace). But the HW seems to be capable
    of accessing these registers - I simply tried bit 3 and it works!
    
    The control register is required to properly reset ATAPI devices or
    they will be detected only once (after a power cycle).
    
    Tested with EXP Computer CD-865 with MC-1285B EPP cable and
    TransDisk 3000.
    
    Signed-off-by: Ondrej Zary <linux@zary.sk>
    Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
Bluetooth: hci_bcm4377: Mark bcm4378/bcm4387 as BROKEN_LE_CODED [+ + +]
Author: Janne Grunau <j@jannau.net>
Date:   Mon Oct 16 09:13:08 2023 +0200

    Bluetooth: hci_bcm4377: Mark bcm4378/bcm4387 as BROKEN_LE_CODED
    
    commit 41e9cdea9c4ab6606ca462ff4ec901a82d022c05 upstream.
    
    bcm4378 and bcm4387 claim to support LE Coded PHY but fail to pair
    (reliably) with BLE devices if it is enabled.
    On bcm4378 pairing usually succeeds after 2-3 tries. On bcm4387
    pairing appears to be completely broken.
    
    Cc: stable@vger.kernel.org # 6.4.y+
    Link: https://discussion.fedoraproject.org/t/mx-master-3-bluetooth-mouse-doesnt-connect/87072/33
    Link: https://github.com/AsahiLinux/linux/issues/177
    Fixes: 288c90224eec ("Bluetooth: Enable all supported LE PHY by default")
    Signed-off-by: Janne Grunau <j@jannau.net>
    Reviewed-by: Eric Curtin <ecurtin@redhat.com>
    Reviewed-by: Neal Gompa <neal@gompa.dev>
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
can: flexcan: remove the auto stop mode for IMX93 [+ + +]
Author: Haibo Chen <haibo.chen@nxp.com>
Date:   Wed Jul 26 19:24:58 2023 +0800

    can: flexcan: remove the auto stop mode for IMX93
    
    [ Upstream commit 63ead535570f13d0e06fda3f2d020c8f5394e998 ]
    
    IMX93 A0 chip involve the internal q-channel handshake in LPCG and
    CCM to automatically handle the Flex-CAN IPG STOP signal. Only after
    FLEX-CAN enter stop mode then can support the self-wakeup feature.
    But meet issue when do the continue system PM stress test. When config
    the CAN as wakeup source, the first time after system suspend, any data
    on CAN bus can wakeup the system, this is as expect. But the second time
    when system suspend, data on CAN bus can't wakeup the system. If continue
    this test, we find in odd time system enter suspend, CAN can wakeup the
    system, but in even number system enter suspend, CAN can't wakeup the
    system. IC find a bug in the auto stop mode logic, and can't fix it easily.
    So for the new imx93 A1, IC drop the auto stop mode and involve the
    GPR to support stop mode (used before). IC define a bit in GPR which can
    trigger the IPG STOP signal to Flex-CAN, let it go into stop mode.
    And NXP claim to drop IMX93 A0, and only support IMX93 A1. So this patch
    remove the auto stop mode, and add flag FLEXCAN_QUIRK_SETUP_STOP_MODE_GPR
    to imx93.
    
    Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
    Link: https://lore.kernel.org/all/20230726112458.3524165-2-haibo.chen@nxp.com
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
ceph_wait_on_conflict_unlink(): grab reference before dropping ->d_lock [+ + +]
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Thu Sep 14 21:55:29 2023 -0400

    ceph_wait_on_conflict_unlink(): grab reference before dropping ->d_lock
    
    [ Upstream commit dc32464a5fe4946fe1a4d8f8e29961dc411933c5 ]
    
    Use of dget() after we'd dropped ->d_lock is too late - dentry might
    be gone by that point.
    
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
coresight: tmc-etr: Disable warnings for allocation failures [+ + +]
Author: Suzuki K Poulose <suzuki.poulose@arm.com>
Date:   Thu Aug 17 17:19:51 2023 +0100

    coresight: tmc-etr: Disable warnings for allocation failures
    
    [ Upstream commit e5028011885a85032aa3c1b7e3e493bcdacb4a0a ]
    
    Running the following command on Juno triggers the warning:
    
     $ perf record -e cs_etm// -m ,128M ...
    
     ------------[ cut here ]------------
     WARNING: CPU: 1 PID: 412 at mm/page_alloc.c:4453 __alloc_pages+0x334/0x1420
     CPU: 1 PID: 412 Comm: perf Not tainted 6.5.0-rc3+ #181
     Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Feb  1 2019
     pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
     pc : __alloc_pages+0x334/0x1420
     lr : dma_common_alloc_pages+0x108/0x138
     sp : ffffffc087fb7440
     x29: ffffffc087fb7440 x28: 0000000000000000 x27: ffffffc07e48fba0
     x26: 0000000000000001 x25: 000000000000000f x24: ffffffc081f24880
     x23: 0000000000000cc0 x22: ffffff88012b6f08 x21: 0000000008000000
     x20: ffffff8801433000 x19: 0000000000000000 x18: 0000000000000000
     x17: ffffffc080316e5c x16: ffffffc07e46406c x15: ffffffc0803af580
     x14: ffffffc08036b460 x13: ffffffc080025cbc x12: ffffffb8108c3fc4
     x11: 1ffffff8108c3fc3 x10: 1ffffff810ff6eac x9 : 00000000f204f204
     x8 : 000000000000f204 x7 : 00000000f2f2f2f2 x6 : 00000000f3f3f3f3
     x5 : 0000000000000001 x4 : 0000000000000000 x3 : 0000000000000000
     x2 : 0000000000000cc0 x1 : 0000000000000000 x0 : ffffffc085333000
     Call trace:
      __alloc_pages+0x334/0x1420
      dma_common_alloc_pages+0x108/0x138
      __dma_alloc_pages+0xf4/0x108
      dma_alloc_pages+0x18/0x30
      tmc_etr_alloc_flat_buf+0xa0/0x190 [coresight_tmc]
      tmc_alloc_etr_buf.constprop.0+0x124/0x298 [coresight_tmc]
      alloc_etr_buf.constprop.0.isra.0+0x88/0xc8 [coresight_tmc]
      tmc_alloc_etr_buffer+0x164/0x2f0 [coresight_tmc]
      etm_setup_aux+0x32c/0x520 [coresight]
      rb_alloc_aux+0x29c/0x3f8
      perf_mmap+0x59c/0xce0
      mmap_region+0x340/0x10e0
      do_mmap+0x48c/0x580
      vm_mmap_pgoff+0x160/0x248
      ksys_mmap_pgoff+0x1e8/0x278
      __arm64_sys_mmap+0x8c/0xb8
    
    With the flat mode, we only attempt to allocate large memory if there is an IOMMU
    connected to the ETR. If the allocation fails, we always have a fallback path
    and return an error if nothing else worked. So, suppress the warning for flat
    mode allocations.
    
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: James Clark <james.clark@arm.com>
    Cc: Anshuman Khandual <anshuman.khandual@arm.com>
    Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Reviewed-by: James Clark <james.clark@arm.com>
    Link: https://lore.kernel.org/r/20230817161951.658534-1-suzuki.poulose@arm.com
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
dmaengine: ste_dma40: Fix PM disable depth imbalance in d40_probe [+ + +]
Author: Zhang Shurong <zhang_shurong@foxmail.com>
Date:   Thu Oct 5 22:28:35 2023 +0800

    dmaengine: ste_dma40: Fix PM disable depth imbalance in d40_probe
    
    [ Upstream commit 0618c077a8c20e8c81e367988f70f7e32bb5a717 ]
    
    The pm_runtime_enable will increase power disable depth. Thus
    a pairing decrement is needed on the error handling path to
    keep it balanced according to context.
    We fix it by calling pm_runtime_disable when error returns.
    
    Signed-off-by: Zhang Shurong <zhang_shurong@foxmail.com>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Link: https://lore.kernel.org/r/tencent_DD2D371DB5925B4B602B1E1D0A5FA88F1208@qq.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
drm/amd/display: Don't use fsleep for PSR exit waits [+ + +]
Author: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Date:   Wed Sep 27 15:06:41 2023 -0400

    drm/amd/display: Don't use fsleep for PSR exit waits
    
    [ Upstream commit 79df45dc4bfb13d9bd3a75338b9d9dab948be3d6 ]
    
    [Why]
    These functions can be called from high IRQ levels and the OS will hang
    if it tries to use a usleep_highres or a msleep.
    
    [How]
    Replace the fsleep with a udelay.
    
    Reviewed-by: Aric Cyr <aric.cyr@amd.com>
    Acked-by: Tom Chung <chiahsuan.chung@amd.com>
    Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
drm/amdgpu: Reserve fences for VM update [+ + +]
Author: Felix Kuehling <Felix.Kuehling@amd.com>
Date:   Mon Jul 17 15:28:52 2023 -0400

    drm/amdgpu: Reserve fences for VM update
    
    [ Upstream commit 316baf09d355aec1179981b6dfe28eba50c5ee5b ]
    
    In amdgpu_dma_buf_move_notify reserve fences for the page table updates
    in amdgpu_vm_clear_freed and amdgpu_vm_handle_moved. This fixes a BUG_ON
    in dma_resv_add_fence when using SDMA for page table updates.
    
    Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

drm/amdgpu: Unset context priority is now invalid [+ + +]
Author: Luben Tuikov <luben.tuikov@amd.com>
Date:   Mon Oct 16 22:24:39 2023 -0400

    drm/amdgpu: Unset context priority is now invalid
    
    [ Upstream commit eab0261967aeab528db4d0a51806df8209aec179 ]
    
    A context priority value of AMD_CTX_PRIORITY_UNSET is now invalid--instead of
    carrying it around and passing it to the Direct Rendering Manager--and it
    becomes AMD_CTX_PRIORITY_NORMAL in amdgpu_ctx_ioctl(), the gateway to context
    creation.
    
    Cc: Alex Deucher <Alexander.Deucher@amd.com>
    Cc: Christian König <christian.koenig@amd.com>
    Signed-off-by: Luben Tuikov <luben.tuikov@amd.com>
    Acked-by: Alex Deucher <Alexander.Deucher@amd.com>
    Link: https://lore.kernel.org/r/20231017035656.8211-1-luben.tuikov@amd.com
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
drm/ttm: Reorder sys manager cleanup step [+ + +]
Author: Karolina Stolarek <karolina.stolarek@intel.com>
Date:   Mon Oct 16 14:15:25 2023 +0200

    drm/ttm: Reorder sys manager cleanup step
    
    [ Upstream commit 3b401e30c249849d803de6c332dad2a595a58658 ]
    
    With the current cleanup flow, we could trigger a NULL pointer
    dereference if there is a delayed destruction of a BO with a
    system resource that gets executed on drain_workqueue() call,
    as we attempt to free a resource using an already released
    resource manager.
    
    Remove the device from the device list and drain its workqueue
    before releasing the system domain manager in ttm_device_fini().
    
    Signed-off-by: Karolina Stolarek <karolina.stolarek@intel.com>
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20231016121525.2237838-1-karolina.stolarek@intel.com
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
dt-bindings: serial: rs485: Add rs485-rts-active-high [+ + +]
Author: Francesco Dolcini <francesco.dolcini@toradex.com>
Date:   Thu Oct 19 17:48:34 2023 +0200

    dt-bindings: serial: rs485: Add rs485-rts-active-high
    
    commit 0c01b20fb50ba63c03841aa83070dc59c3b1b02f upstream.
    
    Add rs485-rts-active-high property, this is a legacy property
    used by 8250_omap.
    
    This fixes the following make dt_binding_check warning:
    
    Documentation/devicetree/bindings/serial/8250_omap.yaml:
    rs485-rts-active-high: missing type definition
    
    Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Closes: https://lore.kernel.org/all/CAMuHMdUkPiA=o_QLyuwsTYW7y1ksCjHAqyNSHFx2QZ-dP-HGsQ@mail.gmail.com/
    Fixes: 403e97d6ab2c ("dt-bindings: serial: 8250_omap: add rs485-rts-active-high")
    Cc: stable <stable@kernel.org>
    Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
    Link: https://lore.kernel.org/r/20231019154834.41721-1-francesco@dolcini.it
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
efi: fix memory leak in krealloc failure handling [+ + +]
Author: Kuan-Wei Chiu <visitorckw@gmail.com>
Date:   Sun Sep 24 22:26:33 2023 +0800

    efi: fix memory leak in krealloc failure handling
    
    [ Upstream commit 0d3ad1917996839a5042d18f04e41915cfa1b74a ]
    
    In the previous code, there was a memory leak issue where the
    previously allocated memory was not freed upon a failed krealloc
    operation. This patch addresses the problem by releasing the old memory
    before setting the pointer to NULL in case of a krealloc failure. This
    ensures that memory is properly managed and avoids potential memory
    leaks.
    
    Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
fbdev: atyfb: only use ioremap_uc() on i386 and ia64 [+ + +]
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Thu Sep 21 19:04:21 2023 +0800

    fbdev: atyfb: only use ioremap_uc() on i386 and ia64
    
    [ Upstream commit c1a8d1d0edb71dec15c9649cb56866c71c1ecd9e ]
    
    ioremap_uc() is only meaningful on old x86-32 systems with the PAT
    extension, and on ia64 with its slightly unconventional ioremap()
    behavior, everywhere else this is the same as ioremap() anyway.
    
    Change the only driver that still references ioremap_uc() to only do so
    on x86-32/ia64 in order to allow removing that interface at some
    point in the future for the other architectures.
    
    On some architectures, ioremap_uc() just returns NULL, changing
    the driver to call ioremap() means that they now have a chance
    of working correctly.
    
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Signed-off-by: Baoquan He <bhe@redhat.com>
    Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Helge Deller <deller@gmx.de>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
    Cc: linux-fbdev@vger.kernel.org
    Cc: dri-devel@lists.freedesktop.org
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fbdev: omapfb: fix some error codes [+ + +]
Author: Dan Carpenter <dan.carpenter@linaro.org>
Date:   Mon Oct 16 14:19:52 2023 +0300

    fbdev: omapfb: fix some error codes
    
    [ Upstream commit dc608db793731426938baa2f0e75a4a3cce5f5cf ]
    
    Return negative -ENXIO instead of positive ENXIO.
    
    Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit() [+ + +]
Author: Jorge Maidana <jorgem.linux@gmail.com>
Date:   Fri Oct 6 17:43:47 2023 -0300

    fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit()
    
    [ Upstream commit 1022e7e2f40574c74ed32c3811b03d26b0b81daf ]
    
    Delete the v86d netlink only after all the VBE tasks have been
    completed.
    
    Fixes initial state restore on module unload:
    uvesafb: VBE state restore call failed (eax=0x4f04, err=-19)
    
    Signed-off-by: Jorge Maidana <jorgem.linux@gmail.com>
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
fs/ntfs3: Add ckeck in ni_update_parent() [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Fri Jun 30 15:52:19 2023 +0400

    fs/ntfs3: Add ckeck in ni_update_parent()
    
    [ Upstream commit 87d1888aa40f25773fa0b948bcb2545f97e2cb15 ]
    
    Check simple case when parent inode equals current inode.
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Add more attributes checks in mi_enum_attr() [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Fri Jun 30 16:17:02 2023 +0400

    fs/ntfs3: Add more attributes checks in mi_enum_attr()
    
    [ Upstream commit 013ff63b649475f0ee134e2c8d0c8e65284ede50 ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Add more info into /proc/fs/ntfs3//volinfo [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Mon Sep 25 10:54:07 2023 +0300

    fs/ntfs3: Add more info into /proc/fs/ntfs3/<dev>/volinfo
    
    [ Upstream commit d27e202b9ac416e52093edf8789614d93dbd6231 ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Avoid possible memory leak [+ + +]
Author: Su Hui <suhui@nfschina.com>
Date:   Mon Sep 25 12:48:07 2023 +0800

    fs/ntfs3: Avoid possible memory leak
    
    [ Upstream commit e4494770a5cad3c9d1d2a65ed15d07656c0d9b82 ]
    
    smatch warn:
    fs/ntfs3/fslog.c:2172 last_log_lsn() warn: possible memory leak of 'page_bufs'
    Jump to label 'out' to free 'page_bufs' and is more consistent with
    other code.
    
    Signed-off-by: Su Hui <suhui@nfschina.com>
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Do not allow to change label if volume is read-only [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Mon Sep 25 10:56:15 2023 +0300

    fs/ntfs3: Do not allow to change label if volume is read-only
    
    [ Upstream commit e52dce610a2d53bf2b5e94a8843c71cb73a91ea5 ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Fix alternative boot searching [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Fri Sep 22 13:12:11 2023 +0300

    fs/ntfs3: Fix alternative boot searching
    
    [ Upstream commit dcc852e509a4cba0ac6ac734077cef260e4e0fe6 ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Fix directory element type detection [+ + +]
Author: Gabriel Marcano <gabemarcano@yahoo.com>
Date:   Tue Sep 12 21:50:32 2023 -0700

    fs/ntfs3: Fix directory element type detection
    
    [ Upstream commit 85a4780dc96ed9dd643bbadf236552b3320fae26 ]
    
    Calling stat() from userspace correctly identified junctions in an NTFS
    partition as symlinks, but using readdir() and iterating through the
    directory containing the same junction did not identify the junction
    as a symlink.
    
    When emitting directory contents, check FILE_ATTRIBUTE_REPARSE_POINT
    attribute to detect junctions and report them as links.
    
    Signed-off-by: Gabriel Marcano <gabemarcano@yahoo.com>
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Fix NULL pointer dereference on error in attr_allocate_frame() [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Tue Sep 26 11:28:11 2023 +0300

    fs/ntfs3: Fix NULL pointer dereference on error in attr_allocate_frame()
    
    [ Upstream commit 9c689c8dc86f8ca99bf91c05f24c8bab38fe7d5f ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Fix possible NULL-ptr-deref in ni_readpage_cmpr() [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Tue Sep 26 11:19:08 2023 +0300

    fs/ntfs3: Fix possible NULL-ptr-deref in ni_readpage_cmpr()
    
    [ Upstream commit 32e9212256b88f35466642f9c939bb40cfb2c2de ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Use kvmalloc instead of kmalloc(... __GFP_NOWARN) [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Fri Jun 30 16:12:58 2023 +0400

    fs/ntfs3: Use kvmalloc instead of kmalloc(... __GFP_NOWARN)
    
    [ Upstream commit fc471e39e38fea6677017cbdd6d928088a59fc67 ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

fs/ntfs3: Write immediately updated ntfs state [+ + +]
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date:   Fri Jun 30 15:57:19 2023 +0400

    fs/ntfs3: Write immediately updated ntfs state
    
    [ Upstream commit 06ccfb00645990a9fcc14249e6d1c25921ecb836 ]
    
    Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
gpu/drm: Eliminate DRM_SCHED_PRIORITY_UNSET [+ + +]
Author: Luben Tuikov <luben.tuikov@amd.com>
Date:   Mon Oct 16 22:48:56 2023 -0400

    gpu/drm: Eliminate DRM_SCHED_PRIORITY_UNSET
    
    [ Upstream commit fa8391ad68c16716e2c06ada397e99ceed2fb647 ]
    
    Eliminate DRM_SCHED_PRIORITY_UNSET, value of -2, whose only user was
    amdgpu. Furthermore, eliminate an index bug, in that when amdgpu boots, it
    calls drm_sched_entity_init() with DRM_SCHED_PRIORITY_UNSET, which uses it to
    index sched->sched_rq[].
    
    Cc: Alex Deucher <Alexander.Deucher@amd.com>
    Cc: Christian König <christian.koenig@amd.com>
    Signed-off-by: Luben Tuikov <luben.tuikov@amd.com>
    Acked-by: Alex Deucher <Alexander.Deucher@amd.com>
    Link: https://lore.kernel.org/r/20231017035656.8211-2-luben.tuikov@amd.com
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport [+ + +]
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Fri Oct 13 17:29:57 2023 -0700

    Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport
    
    [ Upstream commit 5030b2fe6aab37fe42d14f31842ea38be7c55c57 ]
    
    Touch controllers need some time after receiving reset command for the
    firmware to finish re-initializing and be ready to respond to commands
    from the host. The driver already had handling for the post-reset delay
    for I2C and SPI transports, this change adds the handling to
    SMBus-connected devices.
    
    SMBus devices are peculiar because they implement legacy PS/2
    compatibility mode, so reset is actually issued by psmouse driver on the
    associated serio port, after which the control is passed to the RMI4
    driver with SMBus companion device.
    
    Note that originally the delay was added to psmouse driver in
    92e24e0e57f7 ("Input: psmouse - add delay when deactivating for SMBus
    mode"), but that resulted in an unwanted delay in "fast" reconnect
    handler for the serio port, so it was decided to revert the patch and
    have the delay being handled in the RMI4 driver, similar to the other
    transports.
    
    Tested-by: Jeffery Miller <jefferymiller@google.com>
    Link: https://lore.kernel.org/r/ZR1yUFJ8a9Zt606N@penguin
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
io_uring: kiocb_done() should *not* trust ->ki_pos if ->{read,write}_iter() failed [+ + +]
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Mon Aug 28 18:47:31 2023 -0400

    io_uring: kiocb_done() should *not* trust ->ki_pos if ->{read,write}_iter() failed
    
    [ Upstream commit 1939316bf988f3e49a07d9c4dd6f660bf4daa53d ]
    
    ->ki_pos value is unreliable in such cases.  For an obvious example,
    consider O_DSYNC write - we feed the data to page cache and start IO,
    then we make sure it's completed.  Update of ->ki_pos is dealt with
    by the first part; failure in the second ends up with negative value
    returned _and_ ->ki_pos left advanced as if sync had been successful.
    In the same situation write(2) does not advance the file position
    at all.
    
    Reviewed-by: Christian Brauner <brauner@kernel.org>
    Reviewed-by: Jens Axboe <axboe@kernel.dk>
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
irqchip/riscv-intc: Mark all INTC nodes as initialized [+ + +]
Author: Anup Patel <apatel@ventanamicro.com>
Date:   Tue Oct 3 10:13:51 2023 +0530

    irqchip/riscv-intc: Mark all INTC nodes as initialized
    
    [ Upstream commit e13cd66bd821be417c498a34928652db4ac6b436 ]
    
    The RISC-V INTC local interrupts are per-HART (or per-CPU) so we
    create INTC IRQ domain only for the INTC node belonging to the boot
    HART. This means only the boot HART INTC node will be marked as
    initialized and other INTC nodes won't be marked which results
    downstream interrupt controllers (such as PLIC, IMSIC and APLIC
    direct-mode) not being probed due to missing device suppliers.
    
    To address this issue, we mark all INTC node for which we don't
    create IRQ domain as initialized.
    
    Reported-by: Dmitry Dunaev <dunaev@tecon.ru>
    Signed-off-by: Anup Patel <apatel@ventanamicro.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20230926102801.1591126-1-dunaev@tecon.ru
    Link: https://lore.kernel.org/r/20231003044403.1974628-4-apatel@ventanamicro.com
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
irqchip/stm32-exti: add missing DT IRQ flag translation [+ + +]
Author: Ben Wolsieffer <ben.wolsieffer@hefring.com>
Date:   Tue Oct 3 12:20:03 2023 -0400

    irqchip/stm32-exti: add missing DT IRQ flag translation
    
    [ Upstream commit 8554cba1d6dbd3c74e0549e28ddbaccbb1d6b30a ]
    
    The STM32F4/7 EXTI driver was missing the xlate callback, so IRQ trigger
    flags specified in the device tree were being ignored. This was
    preventing the RTC alarm interrupt from working, because it must be set
    to trigger on the rising edge to function correctly.
    
    Signed-off-by: Ben Wolsieffer <ben.wolsieffer@hefring.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20231003162003.1649967-1-ben.wolsieffer@hefring.com
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
Linux: Linux 6.5.11 [+ + +]
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Nov 8 14:09:07 2023 +0100

    Linux 6.5.11
    
    Link: https://lore.kernel.org/r/20231106130305.772449722@linuxfoundation.org
    Tested-by: SeongJae Park <sj@kernel.org>
    Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
    Tested-by: Salvatore Bonaccorso <carnil@debian.org>
    Tested-by: Justin M. Forbes <jforbes@fedoraproject.org>
    Tested-by: Bagas Sanjaya <bagasdotme@gmail.com>
    Tested-by: Ron Economos <re@w6rz.net>
    Tested-by: Jon Hunter <jonathanh@nvidia.com>
    Tested-by: Shuah Khan <skhan@linuxfoundation.org>
    Tested-by: Conor Dooley <conor.dooley@microchip.com>
    Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
    Tested-by: Ricardo B. Marliere <ricardo@marliere.net>
    Tested-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
LoongArch: Disable WUC for pgprot_writecombine() like ioremap_wc() [+ + +]
Author: Icenowy Zheng <uwu@icenowy.me>
Date:   Wed Oct 18 08:42:52 2023 +0800

    LoongArch: Disable WUC for pgprot_writecombine() like ioremap_wc()
    
    [ Upstream commit 278be83601dd1725d4732241f066d528e160a39d ]
    
    Currently the code disables WUC only disables it for ioremap_wc(), which
    is only used when mapping writecombine pages like ioremap() (mapped to
    the kernel space). But for VRAM mapped in TTM/GEM, it is mapped with a
    crafted pgprot by the pgprot_writecombine() function, in which case WUC
    isn't disabled now.
    
    Disable WUC for pgprot_writecombine() (fallback to SUC) if needed, like
    ioremap_wc().
    
    This improves the AMDGPU driver's stability (solves some misrendering)
    on Loongson-3A5000/3A6000 machines.
    
    Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

LoongArch: Export symbol invalid_pud_table for modules building [+ + +]
Author: Huacai Chen <chenhuacai@kernel.org>
Date:   Wed Oct 18 08:42:52 2023 +0800

    LoongArch: Export symbol invalid_pud_table for modules building
    
    [ Upstream commit 449c2756c2323c9e32b2a2fa9c8b59ce91b5819d ]
    
    Export symbol invalid_pud_table for modules building (such as the KVM
    module) if 4-level page tables enabled. Otherwise we get:
    
    ERROR: modpost: "invalid_pud_table" [arch/loongarch/kvm/kvm.ko] undefined!
    
    Reported-by: Randy Dunlap <rdunlap@infradead.org>
    Acked-by: Randy Dunlap <rdunlap@infradead.org>
    Tested-by: Randy Dunlap <rdunlap@infradead.org>
    Signed-off-by: Tianrui Zhao <zhaotianrui@loongson.cn>
    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

LoongArch: Replace kmap_atomic() with kmap_local_page() in copy_user_highpage() [+ + +]
Author: Huacai Chen <chenhuacai@kernel.org>
Date:   Wed Oct 18 08:42:52 2023 +0800

    LoongArch: Replace kmap_atomic() with kmap_local_page() in copy_user_highpage()
    
    [ Upstream commit 477a0ebec101359f49d92796e3b609857d564b52 ]
    
    Replace kmap_atomic()/kunmap_atomic() calls with kmap_local_page()/
    kunmap_local() in copy_user_highpage() which can be invoked from both
    preemptible and atomic context [1].
    
    [1] https://lore.kernel.org/all/20201029222652.302358281@linutronix.de/
    
    Suggested-by: Deepak R Varma <drv@mailo.com>
    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

LoongArch: Use SYM_CODE_* to annotate exception handlers [+ + +]
Author: Tiezhu Yang <yangtiezhu@loongson.cn>
Date:   Wed Oct 18 08:42:52 2023 +0800

    LoongArch: Use SYM_CODE_* to annotate exception handlers
    
    [ Upstream commit 00c2ca84c680f64b79b5e10a482ca435fd7d98ce ]
    
    As described in include/linux/linkage.h,
    
      FUNC -- C-like functions (proper stack frame etc.)
      CODE -- non-C code (e.g. irq handlers with different, special stack etc.)
    
      SYM_FUNC_{START, END} -- use for global functions
      SYM_CODE_{START, END} -- use for non-C (special) functions
    
    So use SYM_CODE_* to annotate exception handlers.
    
    Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
media: i2c: ov8858: Don't set fwnode in the driver [+ + +]
Author: Ondrej Jirman <megi@xff.cz>
Date:   Tue Oct 10 09:07:44 2023 +0200

    media: i2c: ov8858: Don't set fwnode in the driver
    
    [ Upstream commit c46f16f156ac58afcf4addc850bb5dfbca77b9fc ]
    
    This makes the driver work with the new check in
    v4l2_async_register_subdev() that was introduced recently in 6.6-rc1.
    Without this change, probe fails with:
    
    ov8858 1-0036: Detected OV8858 sensor, revision 0xb2
    ov8858 1-0036: sub-device fwnode is an endpoint!
    ov8858 1-0036: v4l2 async register subdev failed
    ov8858: probe of 1-0036 failed with error -22
    
    This also simplifies the driver a bit.
    
    Signed-off-by: Ondrej Jirman <megi@xff.cz>
    Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
    Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
    Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
misc: pci_endpoint_test: Add deviceID for J721S2 PCIe EP device support [+ + +]
Author: Siddharth Vadapalli <s-vadapalli@ti.com>
Date:   Fri Oct 20 17:32:48 2023 +0530

    misc: pci_endpoint_test: Add deviceID for J721S2 PCIe EP device support
    
    commit 8293703a492ae97c86af27c75b76e6239ec86483 upstream.
    
    Add DEVICE_ID for J721S2 and enable support for endpoints configured
    with this DEVICE_ID in the pci_endpoint_test driver.
    
    Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
    Cc: stable <stable@kernel.org>
    Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
    Link: https://lore.kernel.org/r/20231020120248.3168406-1-s-vadapalli@ti.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
mmap: fix error paths with dup_anon_vma() [+ + +]
Author: Liam R. Howlett <Liam.Howlett@oracle.com>
Date:   Fri Sep 29 14:30:40 2023 -0400

    mmap: fix error paths with dup_anon_vma()
    
    commit 824135c46b00df7fb369ec7f1f8607427bbebeb0 upstream.
    
    When the calling function fails after the dup_anon_vma(), the
    duplication of the anon_vma is not being undone.  Add the necessary
    unlink_anon_vma() call to the error paths that are missing them.
    
    This issue showed up during inspection of the error path in vma_merge()
    for an unrelated vma iterator issue.
    
    Users may experience increased memory usage, which may be problematic as
    the failure would likely be caused by a low memory situation.
    
    Link: https://lkml.kernel.org/r/20230929183041.2835469-3-Liam.Howlett@oracle.com
    Fixes: d4af56c5c7c6 ("mm: start tracking VMAs with maple tree")
    Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
    Reviewed-by: Lorenzo Stoakes <lstoakes@gmail.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Jann Horn <jannh@google.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

mmap: fix vma_iterator in error path of vma_merge() [+ + +]
Author: Liam R. Howlett <Liam.Howlett@oracle.com>
Date:   Fri Sep 29 14:30:39 2023 -0400

    mmap: fix vma_iterator in error path of vma_merge()
    
    commit 1419430c8abb5a00590169068590dd54d86590ba upstream.
    
    During the error path, the vma iterator may not be correctly positioned or
    set to the correct range.  Undo the vma_prev() call by resetting to the
    passed in address.  Re-walking to the same range will fix the range to the
    area previously passed in.
    
    Users would notice increased cycles as vma_merge() would be called an
    extra time with vma == prev, and thus would fail to merge and return.
    
    Link: https://lore.kernel.org/linux-mm/CAG48ez12VN1JAOtTNMY+Y2YnsU45yL5giS-Qn=ejtiHpgJAbdQ@mail.gmail.com/
    Link: https://lkml.kernel.org/r/20230929183041.2835469-2-Liam.Howlett@oracle.com
    Fixes: 18b098af2890 ("vma_merge: set vma iterator to correct position.")
    Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
    Reported-by: Jann Horn <jannh@google.com>
    Closes: https://lore.kernel.org/linux-mm/CAG48ez12VN1JAOtTNMY+Y2YnsU45yL5giS-Qn=ejtiHpgJAbdQ@mail.gmail.com/
    Reviewed-by: Lorenzo Stoakes <lstoakes@gmail.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
net/mlx5: Bridge, fix peer entry ageing in LAG mode [+ + +]
Author: Vlad Buslov <vladbu@nvidia.com>
Date:   Wed Aug 9 11:10:57 2023 +0200

    net/mlx5: Bridge, fix peer entry ageing in LAG mode
    
    [ Upstream commit 7a3ce8074878a68a75ceacec93d9ae05906eec86 ]
    
    With current implementation in single FDB LAG mode all packets are
    processed by eswitch 0 rules. As such, 'peer' FDB entries receive the
    packets for rules of other eswitches and are responsible for updating the
    main entry by sending SWITCHDEV_FDB_ADD_TO_BRIDGE notification from their
    background update wq task. However, this introduces a race condition when
    non-zero eswitch instance decides to delete a FDB entry, sends
    SWITCHDEV_FDB_DEL_TO_BRIDGE notification, but another eswitch's update task
    refreshes the same entry concurrently while its async delete work is still
    pending on the workque. In such case another SWITCHDEV_FDB_ADD_TO_BRIDGE
    event may be generated and entry will remain stuck in FDB marked as
    'offloaded' since no more SWITCHDEV_FDB_DEL_TO_BRIDGE notifications are
    sent for deleting the peer entries.
    
    Fix the issue by synchronously marking deleted entries with
    MLX5_ESW_BRIDGE_FLAG_DELETED flag and skipping them in background update
    job.
    
    Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
    Reviewed-by: Jianbo Liu <jianbol@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
net: chelsio: cxgb4: add an error code check in t4_load_phy_fw [+ + +]
Author: Su Hui <suhui@nfschina.com>
Date:   Fri Oct 20 17:27:59 2023 +0800

    net: chelsio: cxgb4: add an error code check in t4_load_phy_fw
    
    [ Upstream commit 9f771493da935299c6393ad3563b581255d01a37 ]
    
    t4_set_params_timeout() can return -EINVAL if failed, add check
    for this.
    
    Signed-off-by: Su Hui <suhui@nfschina.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

net: sched: cls_u32: Fix allocation size in u32_init() [+ + +]
Author: Gustavo A. R. Silva <gustavoars@kernel.org>
Date:   Wed Oct 4 15:19:37 2023 +0200

    net: sched: cls_u32: Fix allocation size in u32_init()
    
    [ Upstream commit c4d49196ceec80e30e8d981410d73331b49b7850 ]
    
    commit d61491a51f7e ("net/sched: cls_u32: Replace one-element array
    with flexible-array member") incorrecly replaced an instance of
    `sizeof(*tp_c)` with `struct_size(tp_c, hlist->ht, 1)`. This results
    in a an over-allocation of 8 bytes.
    
    This change is wrong because `hlist` in `struct tc_u_common` is a
    pointer:
    
    net/sched/cls_u32.c:
    struct tc_u_common {
            struct tc_u_hnode __rcu *hlist;
            void                    *ptr;
            int                     refcnt;
            struct idr              handle_idr;
            struct hlist_node       hnode;
            long                    knodes;
    };
    
    So, the use of `struct_size()` makes no sense: we don't need to allocate
    any extra space for a flexible-array member. `sizeof(*tp_c)` is just fine.
    
    So, `struct_size(tp_c, hlist->ht, 1)` translates to:
    
    sizeof(*tp_c) + sizeof(tp_c->hlist->ht) ==
    sizeof(struct tc_u_common) + sizeof(struct tc_u_knode *) ==
                                                    144 + 8  == 0x98 (byes)
                                                         ^^^
                                                          |
                                                    unnecessary extra
                                                    allocation size
    
    $ pahole -C tc_u_common net/sched/cls_u32.o
    struct tc_u_common {
            struct tc_u_hnode *        hlist;                /*     0     8 */
            void *                     ptr;                  /*     8     8 */
            int                        refcnt;               /*    16     4 */
    
            /* XXX 4 bytes hole, try to pack */
    
            struct idr                 handle_idr;           /*    24    96 */
            /* --- cacheline 1 boundary (64 bytes) was 56 bytes ago --- */
            struct hlist_node          hnode;                /*   120    16 */
            /* --- cacheline 2 boundary (128 bytes) was 8 bytes ago --- */
            long int                   knodes;               /*   136     8 */
    
            /* size: 144, cachelines: 3, members: 6 */
            /* sum members: 140, holes: 1, sum holes: 4 */
            /* last cacheline: 16 bytes */
    };
    
    And with `sizeof(*tp_c)`, we have:
    
            sizeof(*tp_c) == sizeof(struct tc_u_common) == 144 == 0x90 (bytes)
    
    which is the correct and original allocation size.
    
    Fix this issue by replacing `struct_size(tp_c, hlist->ht, 1)` with
    `sizeof(*tp_c)`, and avoid allocating 8 too many bytes.
    
    The following difference in binary output is expected and reflects the
    desired change:
    
    | net/sched/cls_u32.o
    | @@ -6148,7 +6148,7 @@
    | include/linux/slab.h:599
    |     2cf5:      mov    0x0(%rip),%rdi        # 2cfc <u32_init+0xfc>
    |                        2cf8: R_X86_64_PC32     kmalloc_caches+0xc
    |-    2cfc:      mov    $0x98,%edx
    |+    2cfc:      mov    $0x90,%edx
    
    Reported-by: Alejandro Colomar <alx@kernel.org>
    Closes: https://lore.kernel.org/lkml/09b4a2ce-da74-3a19-6961-67883f634d98@kernel.org/
    Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
    Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
netfilter: nf_tables: audit log object reset once per table [+ + +]
Author: Phil Sutter <phil@nwl.cc>
Date:   Wed Oct 11 17:06:59 2023 +0200

    netfilter: nf_tables: audit log object reset once per table
    
    [ Upstream commit 1baf0152f7707c6c7e4ea815dcc1f431c0e603f9 ]
    
    When resetting multiple objects at once (via dump request), emit a log
    message per table (or filled skb) and resurrect the 'entries' parameter
    to contain the number of objects being logged for.
    
    To test the skb exhaustion path, perform some bulk counter and quota
    adds in the kselftest.
    
    Signed-off-by: Phil Sutter <phil@nwl.cc>
    Reviewed-by: Richard Guy Briggs <rgb@redhat.com>
    Acked-by: Paul Moore <paul@paul-moore.com> (Audit)
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

netfilter: nfnetlink_log: silence bogus compiler warning [+ + +]
Author: Florian Westphal <fw@strlen.de>
Date:   Thu Oct 5 10:53:08 2023 +0200

    netfilter: nfnetlink_log: silence bogus compiler warning
    
    [ Upstream commit 2e1d175410972285333193837a4250a74cd472e6 ]
    
    net/netfilter/nfnetlink_log.c:800:18: warning: variable 'ctinfo' is uninitialized
    
    The warning is bogus, the variable is only used if ct is non-NULL and
    always initialised in that case.  Init to 0 too to silence this.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Closes: https://lore.kernel.org/oe-kbuild-all/202309100514.ndBFebXN-lkp@intel.com/
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device [+ + +]
Author: Vicki Pfau <vi@endrift.com>
Date:   Wed Sep 27 13:22:12 2023 -0700

    PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device
    
    commit 7e6f3b6d2c352b5fde37ce3fed83bdf6172eebd4 upstream.
    
    The AMD VanGogh SoC contains a DesignWare USB3 Dual-Role Device that can be
    operated as either a USB Host or a USB Device, similar to on the AMD Nolan
    platform.
    
    be6646bfbaec ("PCI: Prevent xHCI driver from claiming AMD Nolan USB3 DRD
    device") added a quirk to let the dwc3 driver claim the Nolan device since
    it provides more specific support.
    
    Extend that quirk to include the VanGogh SoC USB3 device.
    
    Link: https://lore.kernel.org/r/20230927202212.2388216-1-vi@endrift.com
    Signed-off-by: Vicki Pfau <vi@endrift.com>
    [bhelgaas: include be6646bfbaec reference, add stable tag]
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Cc: stable@vger.kernel.org      # v3.19+
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
perf evlist: Avoid frequency mode for the dummy event [+ + +]
Author: Ian Rogers <irogers@google.com>
Date:   Fri Sep 15 20:56:40 2023 -0700

    perf evlist: Avoid frequency mode for the dummy event
    
    [ Upstream commit f9cdeb58a9cf46c09b56f5f661ea8da24b6458c3 ]
    
    Dummy events are created with an attribute where the period and freq
    are zero. evsel__config will then see the uninitialized values and
    initialize them in evsel__default_freq_period. As fequency mode is
    used by default the dummy event would be set to use frequency
    mode. However, this has no effect on the dummy event but does cause
    unnecessary timers/interrupts. Avoid this overhead by setting the
    period to 1 for dummy events.
    
    evlist__add_aux_dummy calls evlist__add_dummy then sets freq=0 and
    period=1. This isn't necessary after this change and so the setting is
    removed.
    
    From Stephane:
    
    The dummy event is not counting anything. It is used to collect mmap
    records and avoid a race condition during the synthesize mmap phase of
    perf record. As such, it should not cause any overhead during active
    profiling. Yet, it did. Because of a bug the dummy event was
    programmed as a sampling event in frequency mode. Events in that mode
    incur more kernel overheads because on timer tick, the kernel has to
    look at the number of samples for each event and potentially adjust
    the sampling period to achieve the desired frequency. The dummy event
    was therefore adding a frequency event to task and ctx contexts we may
    otherwise not have any, e.g.,
    
      perf record -a -e cpu/event=0x3c,period=10000000/.
    
    On each timer tick the perf_adjust_freq_unthr_context() is invoked and
    if ctx->nr_freq is non-zero, then the kernel will loop over ALL the
    events of the context looking for frequency mode ones. In doing, so it
    locks the context, and enable/disable the PMU of each hw event. If all
    the events of the context are in period mode, the kernel will have to
    traverse the list for nothing incurring overhead. The overhead is
    multiplied by a very large factor when this happens in a guest kernel.
    There is no need for the dummy event to be in frequency mode, it does
    not count anything and therefore should not cause extra overhead for
    no reason.
    
    Fixes: 5bae0250237f ("perf evlist: Introduce perf_evlist__new_dummy constructor")
    Reported-by: Stephane Eranian <eranian@google.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Acked-by: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Yang Jihong <yangjihong1@huawei.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Link: https://lore.kernel.org/r/20230916035640.1074422-1-irogers@google.com
    Signed-off-by: Namhyung Kim <namhyung@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
platform/mellanox: mlxbf-tmfifo: Fix a warning message [+ + +]
Author: Liming Sun <limings@nvidia.com>
Date:   Thu Oct 12 19:02:35 2023 -0400

    platform/mellanox: mlxbf-tmfifo: Fix a warning message
    
    [ Upstream commit 99c09c985e5973c8f0ad976ebae069548dd86f12 ]
    
    This commit fixes the smatch static checker warning in function
    mlxbf_tmfifo_rxtx_word() which complains data not initialized at
    line 634 when IS_VRING_DROP() is TRUE.
    
    Signed-off-by: Liming Sun <limings@nvidia.com>
    Link: https://lore.kernel.org/r/20231012230235.219861-1-limings@nvidia.com
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
power: supply: core: Use blocking_notifier_call_chain to avoid RCU complaint [+ + +]
Author: Kai-Heng Feng <kai.heng.feng@canonical.com>
Date:   Wed Sep 13 11:32:33 2023 +0800

    power: supply: core: Use blocking_notifier_call_chain to avoid RCU complaint
    
    [ Upstream commit bbaa6ffa5b6c9609d3b3c431c389b407eea5441f ]
    
    AMD PMF driver can cause the following warning:
    [  196.159546] ------------[ cut here ]------------
    [  196.159556] Voluntary context switch within RCU read-side critical section!
    [  196.159571] WARNING: CPU: 0 PID: 9 at kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x43d/0x560
    [  196.159604] Modules linked in: nvme_fabrics ccm rfcomm snd_hda_scodec_cs35l41_spi cmac algif_hash algif_skcipher af_alg bnep joydev btusb btrtl uvcvideo btintel btbcm videobuf2_vmalloc intel_rapl_msr btmtk videobuf2_memops uvc videobuf2_v4l2 intel_rapl_common binfmt_misc hid_sensor_als snd_sof_amd_vangogh hid_sensor_trigger bluetooth industrialio_triggered_buffer videodev snd_sof_amd_rembrandt hid_sensor_iio_common amdgpu ecdh_generic kfifo_buf videobuf2_common hp_wmi kvm_amd sparse_keymap snd_sof_amd_renoir wmi_bmof industrialio ecc mc nls_iso8859_1 kvm snd_sof_amd_acp irqbypass snd_sof_xtensa_dsp crct10dif_pclmul crc32_pclmul mt7921e snd_sof_pci snd_ctl_led polyval_clmulni mt7921_common polyval_generic snd_sof ghash_clmulni_intel mt792x_lib mt76_connac_lib sha512_ssse3 snd_sof_utils aesni_intel snd_hda_codec_realtek crypto_simd mt76 snd_hda_codec_generic cryptd snd_soc_core snd_hda_codec_hdmi rapl ledtrig_audio input_leds snd_compress i2c_algo_bit drm_ttm_helper mac80211 snd_pci_ps hid_multitouch ttm drm_exec
    [  196.159970]  drm_suballoc_helper snd_rpl_pci_acp6x amdxcp drm_buddy snd_hda_intel snd_acp_pci snd_hda_scodec_cs35l41_i2c serio_raw gpu_sched snd_hda_scodec_cs35l41 snd_acp_legacy_common snd_intel_dspcfg snd_hda_cs_dsp_ctls snd_hda_codec libarc4 drm_display_helper snd_pci_acp6x cs_dsp snd_hwdep snd_soc_cs35l41_lib video k10temp snd_pci_acp5x thunderbolt snd_hda_core drm_kms_helper cfg80211 snd_seq snd_rn_pci_acp3x snd_pcm snd_acp_config cec snd_soc_acpi snd_seq_device rc_core ccp snd_pci_acp3x snd_timer snd soundcore wmi amd_pmf platform_profile amd_pmc mac_hid serial_multi_instantiate wireless_hotkey hid_sensor_hub sch_fq_codel msr parport_pc ppdev lp parport efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log cdc_ether usbnet r8152 mii hid_generic nvme i2c_hid_acpi i2c_hid nvme_core i2c_piix4 xhci_pci amd_sfh drm xhci_pci_renesas nvme_common hid
    [  196.160382] CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.6.0-rc1 #4
    [  196.160397] Hardware name: HP HP EliteBook 845 14 inch G10 Notebook PC/8B6E, BIOS V82 Ver. 01.02.00 08/24/2023
    [  196.160405] Workqueue: events power_supply_changed_work
    [  196.160426] RIP: 0010:rcu_note_context_switch+0x43d/0x560
    [  196.160440] Code: 00 48 89 be 40 08 00 00 48 89 86 48 08 00 00 48 89 10 e9 63 fe ff ff 48 c7 c7 10 e7 b0 9e c6 05 e8 d8 20 02 01 e8 13 0f f3 ff <0f> 0b e9 27 fc ff ff a9 ff ff ff 7f 0f 84 cf fc ff ff 65 48 8b 3c
    [  196.160450] RSP: 0018:ffffc900001878f0 EFLAGS: 00010046
    [  196.160462] RAX: 0000000000000000 RBX: ffff88885e834040 RCX: 0000000000000000
    [  196.160470] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
    [  196.160476] RBP: ffffc90000187910 R08: 0000000000000000 R09: 0000000000000000
    [  196.160482] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
    [  196.160488] R13: 0000000000000000 R14: ffff888100990000 R15: ffff888100990000
    [  196.160495] FS:  0000000000000000(0000) GS:ffff88885e800000(0000) knlGS:0000000000000000
    [  196.160504] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  196.160512] CR2: 000055cb053c8246 CR3: 000000013443a000 CR4: 0000000000750ef0
    [  196.160520] PKRU: 55555554
    [  196.160526] Call Trace:
    [  196.160532]  <TASK>
    [  196.160548]  ? show_regs+0x72/0x90
    [  196.160570]  ? rcu_note_context_switch+0x43d/0x560
    [  196.160580]  ? __warn+0x8d/0x160
    [  196.160600]  ? rcu_note_context_switch+0x43d/0x560
    [  196.160613]  ? report_bug+0x1bb/0x1d0
    [  196.160637]  ? handle_bug+0x46/0x90
    [  196.160658]  ? exc_invalid_op+0x19/0x80
    [  196.160675]  ? asm_exc_invalid_op+0x1b/0x20
    [  196.160709]  ? rcu_note_context_switch+0x43d/0x560
    [  196.160727]  __schedule+0xb9/0x15f0
    [  196.160746]  ? srso_alias_return_thunk+0x5/0x7f
    [  196.160765]  ? srso_alias_return_thunk+0x5/0x7f
    [  196.160778]  ? acpi_ns_search_one_scope+0xbe/0x270
    [  196.160806]  schedule+0x68/0x110
    [  196.160820]  schedule_timeout+0x151/0x160
    [  196.160829]  ? srso_alias_return_thunk+0x5/0x7f
    [  196.160842]  ? srso_alias_return_thunk+0x5/0x7f
    [  196.160855]  ? acpi_ns_lookup+0x3c5/0xa90
    [  196.160878]  __down_common+0xff/0x220
    [  196.160905]  __down_timeout+0x16/0x30
    [  196.160920]  down_timeout+0x64/0x70
    [  196.160938]  acpi_os_wait_semaphore+0x85/0x200
    [  196.160959]  acpi_ut_acquire_mutex+0x9e/0x280
    [  196.160979]  acpi_ex_enter_interpreter+0x2d/0xb0
    [  196.160992]  acpi_ns_evaluate+0x2f0/0x5f0
    [  196.161005]  acpi_evaluate_object+0x172/0x490
    [  196.161018]  ? acpi_os_signal_semaphore+0x8a/0xd0
    [  196.161038]  acpi_evaluate_integer+0x52/0xe0
    [  196.161055]  ? kfree+0x79/0x120
    [  196.161071]  ? srso_alias_return_thunk+0x5/0x7f
    [  196.161089]  acpi_ac_get_state.part.0+0x27/0x80
    [  196.161110]  get_ac_property+0x5c/0x70
    [  196.161127]  ? __pfx___power_supply_is_system_supplied+0x10/0x10
    [  196.161146]  __power_supply_is_system_supplied+0x44/0xb0
    [  196.161166]  class_for_each_device+0x124/0x160
    [  196.161184]  ? acpi_ac_get_state.part.0+0x27/0x80
    [  196.161203]  ? srso_alias_return_thunk+0x5/0x7f
    [  196.161223]  power_supply_is_system_supplied+0x3c/0x70
    [  196.161243]  amd_pmf_get_power_source+0xe/0x20 [amd_pmf]
    [  196.161276]  amd_pmf_power_slider_update_event+0x49/0x90 [amd_pmf]
    [  196.161310]  amd_pmf_pwr_src_notify_call+0xe7/0x100 [amd_pmf]
    [  196.161340]  notifier_call_chain+0x5f/0xe0
    [  196.161362]  atomic_notifier_call_chain+0x33/0x60
    [  196.161378]  power_supply_changed_work+0x84/0x110
    [  196.161394]  process_one_work+0x178/0x360
    [  196.161412]  ? __pfx_worker_thread+0x10/0x10
    [  196.161424]  worker_thread+0x307/0x430
    [  196.161440]  ? __pfx_worker_thread+0x10/0x10
    [  196.161451]  kthread+0xf4/0x130
    [  196.161467]  ? __pfx_kthread+0x10/0x10
    [  196.161486]  ret_from_fork+0x43/0x70
    [  196.161502]  ? __pfx_kthread+0x10/0x10
    [  196.161518]  ret_from_fork_asm+0x1b/0x30
    [  196.161558]  </TASK>
    [  196.161562] ---[ end trace 0000000000000000 ]---
    
    Since there's no guarantee that all the callbacks can work in atomic
    context, switch to use blocking_notifier_call_chain to relax the
    constraint.
    
    Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
    Reported-by: Allen Zhong <allen@atr.me>
    Fixes: 4c71ae414474 ("platform/x86/amd/pmf: Add support SPS PMF feature")
    Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217571
    Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
    Link: https://lore.kernel.org/r/20230913033233.602986-1-kai.heng.feng@canonical.com
    Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
powerpc/85xx: Fix math emulation exception [+ + +]
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Mon Sep 25 17:55:51 2023 +0200

    powerpc/85xx: Fix math emulation exception
    
    [ Upstream commit 8e8a12ecbc86700b5e1a3596ce2b3c43dafad336 ]
    
    Booting mpc85xx_defconfig kernel on QEMU leads to:
    
    Bad trap at PC: fe9bab0, SR: 2d000, vector=800
    awk[82]: unhandled trap (5) at 0 nip fe9bab0 lr fe9e01c code 5 in libc-2.27.so[fe5a000+17a000]
    awk[82]: code: 3aa00000 3a800010 4bffe03c 9421fff0 7ca62b78 38a00000 93c10008 83c10008
    awk[82]: code: 38210010 4bffdec8 9421ffc0 7c0802a6 <fc00048e> d8010008 4815190d 93810030
    Trace/breakpoint trap
    WARNING: no useful console
    
    This is because allthough CONFIG_MATH_EMULATION is selected,
    Exception 800 calls unknown_exception().
    
    Call emulation_assist_interrupt() instead.
    
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://msgid.link/066caa6d9480365da9b8ed83692d7101e10ac5f8.1695657339.git.christophe.leroy@csgroup.eu
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
powerpc/mm: Fix boot crash with FLATMEM [+ + +]
Author: Michael Ellerman <mpe@ellerman.id.au>
Date:   Mon Oct 23 22:25:00 2023 +1100

    powerpc/mm: Fix boot crash with FLATMEM
    
    [ Upstream commit daa9ada2093ed23d52b4c1fe6e13cf78f55cc85f ]
    
    Erhard reported that his G5 was crashing with v6.6-rc kernels:
    
      mpic: Setting up HT PICs workarounds for U3/U4
      BUG: Unable to handle kernel data access at 0xfeffbb62ffec65fe
      Faulting instruction address: 0xc00000000005dc40
      Oops: Kernel access of bad area, sig: 11 [#1]
      BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
      Modules linked in:
      CPU: 0 PID: 0 Comm: swapper/0 Tainted: G                T  6.6.0-rc3-PMacGS #1
      Hardware name: PowerMac11,2 PPC970MP 0x440101 PowerMac
      NIP:  c00000000005dc40 LR: c000000000066660 CTR: c000000000007730
      REGS: c0000000022bf510 TRAP: 0380   Tainted: G                T (6.6.0-rc3-PMacGS)
      MSR:  9000000000001032 <SF,HV,ME,IR,DR,RI>  CR: 44004242  XER: 00000000
      IRQMASK: 3
      GPR00: 0000000000000000 c0000000022bf7b0 c0000000010c0b00 00000000000001ac
      GPR04: 0000000003c80000 0000000000000300 c0000000f20001ae 0000000000000300
      GPR08: 0000000000000006 feffbb62ffec65ff 0000000000000001 0000000000000000
      GPR12: 9000000000001032 c000000002362000 c000000000f76b80 000000000349ecd8
      GPR16: 0000000002367ba8 0000000002367f08 0000000000000006 0000000000000000
      GPR20: 00000000000001ac c000000000f6f920 c0000000022cd985 000000000000000c
      GPR24: 0000000000000300 00000003b0a3691d c0003e008030000e 0000000000000000
      GPR28: c00000000000000c c0000000f20001ee feffbb62ffec65fe 00000000000001ac
      NIP hash_page_do_lazy_icache+0x50/0x100
      LR  __hash_page_4K+0x420/0x590
      Call Trace:
        hash_page_mm+0x364/0x6f0
        do_hash_fault+0x114/0x2b0
        data_access_common_virt+0x198/0x1f0
      --- interrupt: 300 at mpic_init+0x4bc/0x10c4
      NIP:  c000000002020a5c LR: c000000002020a04 CTR: 0000000000000000
      REGS: c0000000022bf9f0 TRAP: 0300   Tainted: G                T (6.6.0-rc3-PMacGS)
      MSR:  9000000000001032 <SF,HV,ME,IR,DR,RI>  CR: 24004248  XER: 00000000
      DAR: c0003e008030000e DSISR: 40000000 IRQMASK: 1
      ...
      NIP mpic_init+0x4bc/0x10c4
      LR  mpic_init+0x464/0x10c4
      --- interrupt: 300
        pmac_setup_one_mpic+0x258/0x2dc
        pmac_pic_init+0x28c/0x3d8
        init_IRQ+0x90/0x140
        start_kernel+0x57c/0x78c
        start_here_common+0x1c/0x20
    
    A bisect pointed to the breakage beginning with commit 9fee28baa601 ("powerpc:
    implement the new page table range API").
    
    Analysis of the oops pointed to a struct page with a corrupted
    compound_head being loaded via page_folio() -> _compound_head() in
    hash_page_do_lazy_icache().
    
    The access by the mpic code is to an MMIO address, so the expectation
    is that the struct page for that address would be initialised by
    init_unavailable_range(), as pointed out by Aneesh.
    
    Instrumentation showed that was not the case, which eventually lead to
    the realisation that pfn_valid() was returning false for that address,
    causing the struct page to not be initialised.
    
    Because the system is using FLATMEM, the version of pfn_valid() in
    memory_model.h is used:
    
    static inline int pfn_valid(unsigned long pfn)
    {
            ...
            return pfn >= pfn_offset && (pfn - pfn_offset) < max_mapnr;
    }
    
    Which relies on max_mapnr being initialised. Early in boot max_mapnr is
    zero meaning no PFNs are valid.
    
    max_mapnr is initialised in mem_init() called via:
    
      start_kernel()
        mm_core_init()  # init/main.c:928
          mem_init()
    
    But that is too late for the usage in init_unavailable_range() called via:
    
      start_kernel()
        setup_arch()    # init/main.c:893
          paging_init()
            free_area_init()
              init_unavailable_range()
    
    Although max_mapnr is currently set in mem_init(), the value is actually
    already available much earlier, as soon as mem_topology_setup() has
    completed, which is also before paging_init() is called. So move the
    initialisation there, which causes paging_init() to correctly initialise
    the struct page and fixes the bug.
    
    This bug seems to have been lurking for years, but went unnoticed
    because the pre-folio code was inspecting the uninitialised page->flags
    but not dereferencing it.
    
    Thanks to Erhard and Aneesh for help debugging.
    
    Reported-by: Erhard Furtner <erhard_f@mailbox.org>
    Closes: https://lore.kernel.org/all/20230929132750.3cd98452@yea/
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://msgid.link/20231023112500.1550208-1-mpe@ellerman.id.au
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en() [+ + +]
Author: Douglas Anderson <dianders@chromium.org>
Date:   Fri Oct 20 14:06:57 2023 -0700

    r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en()
    
    [ Upstream commit bc65cc42af737a5a35f83842408ef2c6c79ba025 ]
    
    If the adapter is unplugged while we're looping in r8153b_ups_en() /
    r8153c_ups_en() we could end up looping for 10 seconds (20 ms * 500
    loops). Add code similar to what's done in other places in the driver
    to check for unplug and bail.
    
    Signed-off-by: Douglas Anderson <dianders@chromium.org>
    Reviewed-by: Grant Grundler <grundler@chromium.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

r8152: Check for unplug in rtl_phy_patch_request() [+ + +]
Author: Douglas Anderson <dianders@chromium.org>
Date:   Fri Oct 20 14:06:56 2023 -0700

    r8152: Check for unplug in rtl_phy_patch_request()
    
    [ Upstream commit dc90ba37a8c37042407fa6970b9830890cfe6047 ]
    
    If the adapter is unplugged while we're looping in
    rtl_phy_patch_request() we could end up looping for 10 seconds (2 ms *
    5000 loops). Add code similar to what's done in other places in the
    driver to check for unplug and bail.
    
    Signed-off-by: Douglas Anderson <dianders@chromium.org>
    Reviewed-by: Grant Grundler <grundler@chromium.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
riscv: dts: thead: set dma-noncoherent to soc bus [+ + +]
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Tue Sep 12 15:22:32 2023 +0800

    riscv: dts: thead: set dma-noncoherent to soc bus
    
    [ Upstream commit 759426c758c7053a941a4c06c7571461439fcff6 ]
    
    riscv select ARCH_DMA_DEFAULT_COHERENT by default, and th1520 isn't
    dma coherent, so set dma-noncoherent to reflect this fact.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Tested-by: Drew Fustini <dfustini@baylibre.com>
    Reviewed-by: Guo Ren <guoren@kernel.org>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
rust: make `UnsafeCell` the outer type in `Opaque` [+ + +]
Author: Alice Ryhl <aliceryhl@google.com>
Date:   Wed Jun 14 11:53:28 2023 +0000

    rust: make `UnsafeCell` the outer type in `Opaque`
    
    [ Upstream commit 35cad617df2eeef8440a38e82bb2d81ae32ca50d ]
    
    When combining `UnsafeCell` with `MaybeUninit`, it is idiomatic to use
    `UnsafeCell` as the outer type. Intuitively, this is because a
    `MaybeUninit<T>` might not contain a `T`, but we always want the effect
    of the `UnsafeCell`, even if the inner value is uninitialized.
    
    Now, strictly speaking, this doesn't really make a difference. The
    compiler will always apply the `UnsafeCell` effect even if the inner
    value is uninitialized. But I think we should follow the convention
    here.
    
    Signed-off-by: Alice Ryhl <aliceryhl@google.com>
    Reviewed-by: Benno Lossin <benno.lossin@proton.me>
    Reviewed-by: Gary Guo <gary@garyguo.net>
    Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
    Link: https://lore.kernel.org/r/20230614115328.2825961-1-aliceryhl@google.com
    Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
    Stable-dep-of: 0b4e3b6f6b79 ("rust: types: make `Opaque` be `!Unpin`")
    Signed-off-by: Sasha Levin <sashal@kernel.org>

rust: types: make `Opaque` be `!Unpin` [+ + +]
Author: Benno Lossin <benno.lossin@proton.me>
Date:   Fri Jun 30 15:03:23 2023 +0000

    rust: types: make `Opaque` be `!Unpin`
    
    [ Upstream commit 0b4e3b6f6b79b1add04008a6ceaaf661107e8902 ]
    
    Adds a `PhantomPinned` field to `Opaque<T>`. This removes the last Rust
    guarantee: the assumption that the type `T` can be freely moved. This is
    not the case for many types from the C side (e.g. if they contain a
    `struct list_head`). This change removes the need to add a
    `PhantomPinned` field manually to Rust structs that contain C structs
    which must not be moved.
    
    Signed-off-by: Benno Lossin <benno.lossin@proton.me>
    Reviewed-by: Gary Guo <gary@garyguo.net>
    Reviewed-by: Alice Ryhl <aliceryhl@google.com>
    Reviewed-by: Andreas Hindborg <a.hindborg@samsung.com>
    Link: https://lore.kernel.org/r/20230630150216.109789-1-benno.lossin@proton.me
    Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
s390/kasan: handle DCSS mapping in memory holes [+ + +]
Author: Vasily Gorbik <gor@linux.ibm.com>
Date:   Thu Oct 12 11:06:21 2023 +0200

    s390/kasan: handle DCSS mapping in memory holes
    
    [ Upstream commit 327899674eef18f96644be87aa5510b7523fe4f6 ]
    
    When physical memory is defined under z/VM using DEF STOR CONFIG, there
    may be memory holes that are not hotpluggable memory. In such cases,
    DCSS mapping could be placed in one of these memory holes. Subsequently,
    attempting memory access to such DCSS mapping would result in a kasan
    failure because there is no shadow memory mapping for it.
    
    To maintain consistency with cases where DCSS mapping is positioned after
    the kernel identity mapping, which is then covered by kasan zero shadow
    mapping, handle the scenario above by populating zero shadow mapping
    for memory holes where DCSS mapping could potentially be placed.
    
    Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
    Reviewed-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
scsi: mpt3sas: Fix in error path [+ + +]
Author: Tomas Henzl <thenzl@redhat.com>
Date:   Sun Oct 15 13:45:29 2023 +0200

    scsi: mpt3sas: Fix in error path
    
    [ Upstream commit e40c04ade0e2f3916b78211d747317843b11ce10 ]
    
    The driver should be deregistered as misc driver after PCI registration
    failure.
    
    Signed-off-by: Tomas Henzl <thenzl@redhat.com>
    Link: https://lore.kernel.org/r/20231015114529.10725-1-thenzl@redhat.com
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
serial: core: Fix runtime PM handling for pending tx [+ + +]
Author: Tony Lindgren <tony@atomide.com>
Date:   Mon Oct 23 10:48:54 2023 +0300

    serial: core: Fix runtime PM handling for pending tx
    
    commit 6f699743aebf07538e506a46c5965eb8bdd2c716 upstream.
    
    Richard reported that a serial port may end up sometimes with tx data
    pending in the buffer for long periods of time.
    
    Turns out we bail out early on any errors from pm_runtime_get(),
    including -EINPROGRESS. To fix the issue, we need to ignore -EINPROGRESS
    as we only care about the runtime PM usage count at this point. We check
    for an active runtime PM state later on for tx.
    
    Fixes: 84a9582fd203 ("serial: core: Start managing serial controllers to enable runtime PM")
    Cc: stable <stable@kernel.org>
    Reported-by: Richard Purdie <richard.purdie@linuxfoundation.org>
    Cc: Bruce Ashfield <bruce.ashfield@gmail.com>
    Cc: Mikko Rapeli <mikko.rapeli@linaro.org>
    Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
    Cc: Randy MacLeod <randy.macleod@windriver.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
    Tested-by: Richard Purdie <richard.purdie@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20231023074856.61896-1-tony@atomide.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0 [+ + +]
Author: William A. Kennington III <william@wkennington.com>
Date:   Fri Sep 22 11:28:12 2023 -0700

    spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
    
    [ Upstream commit 2ec8b010979036c2fe79a64adb6ecc0bd11e91d1 ]
    
    We don't want to use the value of ilog2(0) as dummy.buswidth is 0 when
    dummy.nbytes is 0. Since we have no dummy bytes, we don't need to
    configure the dummy byte bits per clock register value anyway.
    
    Signed-off-by: "William A. Kennington III" <william@wkennington.com>
    Link: https://lore.kernel.org/r/20230922182812.2728066-1-william@wkennington.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
tty: 8250: Add Brainboxes Oxford Semiconductor-based quirks [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:17 2023 +0100

    tty: 8250: Add Brainboxes Oxford Semiconductor-based quirks
    
    commit e4876dacaca46a1b09f9b417480924ab12019a5b upstream.
    
    Some of the later revisions of the Brainboxes PX cards are based
    on the Oxford Semiconductor chipset. Due to the chip's unique setup
    these cards need to be initialised.
    Previously these were tested against a reference card with the same broken
    baudrate on another PC, cancelling out the effect. With this patch they
    work and can transfer/receive find against an FTDI-based device.
    
    Add all of the cards which require this setup to the quirks table.
    Thanks to Maciej W. Rozycki for clarification on this chip.
    
    Fixes: ef5a03a26c87 ("tty: 8250: Add support for Brainboxes PX cards.")
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB7899D222A4AB2A4E8C57108FC4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Add support for additional Brainboxes PX cards [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:15 2023 +0100

    tty: 8250: Add support for additional Brainboxes PX cards
    
    commit 9604884e592cd04ead024c9737c67a77f175cab9 upstream.
    
    Add support for some more of the Brainboxes PX (PCIe) range
    of serial cards, namely
    PX-275/PX-279, PX-475 (serial port, not LPT), PX-820,
    PX-803/PX-857 (additional ID).
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB78996BEC353FB346FC35444BC4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Add support for additional Brainboxes UC cards [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:09 2023 +0100

    tty: 8250: Add support for additional Brainboxes UC cards
    
    commit c563db486db7d245c0e2f319443417ae8e692f7f upstream.
    
    Add device IDs for some more Brainboxes UC cards, namely
    UC-235/UC-246, UC-253/UC-734, UC-302, UC-313, UC-346, UC-357,
    UC-607 and UC-836.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB789969998A6C3FAFCD95C85DC4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Add support for Brainboxes UP cards [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:10 2023 +0100

    tty: 8250: Add support for Brainboxes UP cards
    
    commit 2c6fec1e1532f15350be7e14ba6b88a39d289fe4 upstream.
    
    Add support for the Brainboxes UP (powered PCI) range of
    cards, namely UP-189, UP-200, UP-869 and UP-880.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB7899B5B59FF3D8587E88C117C4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Add support for Intashield IS-100 [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:11 2023 +0100

    tty: 8250: Add support for Intashield IS-100
    
    commit 4d994e3cf1b541ff32dfb03fbbc60eea68f9645b upstream.
    
    Add support for the Intashield IS-100 1 port serial card.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB7899A0E0CDAA505AF5A874CDC4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Add support for Intashield IX cards [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:16 2023 +0100

    tty: 8250: Add support for Intashield IX cards
    
    commit 62d2ec2ded278c7512d91ca7bf8eb9bac46baf90 upstream.
    
    Add support for the IX-100, IX-200 and IX-400 serial cards.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB7899614E5837E82A03272A4BC4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Fix port count of PX-257 [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:12 2023 +0100

    tty: 8250: Fix port count of PX-257
    
    commit d0ff5b24c2f112f29dea4c38b3bac9597b1be9ba upstream.
    
    The port count of the PX-257 Rev3 is actually 2, not 4.
    
    Fixes: ef5a03a26c87 ("tty: 8250: Add support for Brainboxes PX cards.")
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB7899C804D9F04E727B5A0E8FC4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Fix up PX-803/PX-857 [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:13 2023 +0100

    tty: 8250: Fix up PX-803/PX-857
    
    commit ee61337b934c99c2611e0a945d592019b2e00c82 upstream.
    
    The PX-803/PX-857 are variants of each other, add a note.
    Additionally fix up the port counts for the card (2, not 1).
    
    Fixes: ef5a03a26c87 ("tty: 8250: Add support for Brainboxes PX cards.")
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB789978C8ED872FB4B014E132C4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: 8250: Remove UC-257 and UC-431 [+ + +]
Author: Cameron Williams <cang1@live.co.uk>
Date:   Fri Oct 20 17:03:08 2023 +0100

    tty: 8250: Remove UC-257 and UC-431
    
    commit 33092fb3af51deb80849e90a17bada44bbcde6b3 upstream.
    
    The UC-257 is a serial + LPT card, so remove it from this driver.
    A patch has been submitted to add it to parport_serial instead.
    
    Additionaly, the UC-431 does not use this card ID, only the UC-420
    does. The 431 is a 3-port card and there is no generic 3-port configuration
    available, so remove reference to it from this driver.
    
    Fixes: 152d1afa834c ("tty: Add support for Brainboxes UC cards.")
    Cc: stable@vger.kernel.org
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Link: https://lore.kernel.org/r/DU0PR02MB78995ADF7394C74AD4CF3357C4DBA@DU0PR02MB7899.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

tty: n_gsm: fix race condition in status line change on dead connections [+ + +]
Author: Daniel Starke <daniel.starke@siemens.com>
Date:   Thu Oct 26 07:58:43 2023 +0200

    tty: n_gsm: fix race condition in status line change on dead connections
    
    commit 3a75b205de43365f80a33b98ec9289785da56243 upstream.
    
    gsm_cleanup_mux() cleans up the gsm by closing all DLCIs, stopping all
    timers, removing the virtual tty devices and clearing the data queues.
    This procedure, however, may cause subsequent changes of the virtual modem
    status lines of a DLCI. More data is being added the outgoing data queue
    and the deleted kick timer is restarted to handle this. At this point many
    resources have already been removed by the cleanup procedure. Thus, a
    kernel panic occurs.
    
    Fix this by proving in gsm_modem_update() that the cleanup procedure has
    not been started and the mux is still alive.
    
    Note that writing to a virtual tty is already protected by checks against
    the DLCI specific connection state.
    
    Fixes: c568f7086c6e ("tty: n_gsm: fix missing timer to handle stalled links")
    Cc: stable <stable@kernel.org>
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20231026055844.3127-1-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
usb: raw-gadget: properly handle interrupted requests [+ + +]
Author: Andrey Konovalov <andreyknvl@gmail.com>
Date:   Thu Oct 26 22:01:12 2023 +0200

    usb: raw-gadget: properly handle interrupted requests
    
    commit e8033bde451eddfb9b1bbd6e2d848c1b5c277222 upstream.
    
    Currently, if a USB request that was queued by Raw Gadget is interrupted
    (via a signal), wait_for_completion_interruptible returns -ERESTARTSYS.
    Raw Gadget then attempts to propagate this value to userspace as a return
    value from its ioctls. However, when -ERESTARTSYS is returned by a syscall
    handler, the kernel internally restarts the syscall.
    
    This doesn't allow userspace applications to interrupt requests queued by
    Raw Gadget (which is required when the emulated device is asked to switch
    altsettings). It also violates the implied interface of Raw Gadget that a
    single ioctl must only queue a single USB request.
    
    Instead, make Raw Gadget do what GadgetFS does: check whether the request
    was interrupted (dequeued with status == -ECONNRESET) and report -EINTR to
    userspace.
    
    Fixes: f2c2e717642c ("usb: gadget: add raw-gadget interface")
    Cc: stable <stable@kernel.org>
    Signed-off-by: Andrey Konovalov <andreyknvl@gmail.com>
    Link: https://lore.kernel.org/r/0db45b1d7cc466e3d4d1ab353f61d63c977fbbc5.1698350424.git.andreyknvl@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

usb: storage: set 1.50 as the lower bcdDevice for older "Super Top" compatibility [+ + +]
Author: LihaSika <lihasika@gmail.com>
Date:   Fri Oct 27 20:28:04 2023 +0300

    usb: storage: set 1.50 as the lower bcdDevice for older "Super Top" compatibility
    
    commit 0e3139e6543b241b3e65956a55c712333bef48ac upstream.
    
    Change lower bcdDevice value for "Super Top USB 2.0  SATA BRIDGE" to match
    1.50. I have such an older device with bcdDevice=1.50 and it will not work
    otherwise.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Liha Sikanen <lihasika@gmail.com>
    Link: https://lore.kernel.org/r/ccf7d12a-8362-4916-b3e0-f4150f54affd@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

usb: typec: tcpm: Add additional checks for contaminant [+ + +]
Author: Badhri Jagan Sridharan <badhri@google.com>
Date:   Sun Oct 15 05:31:08 2023 +0000

    usb: typec: tcpm: Add additional checks for contaminant
    
    commit 1a4a2df07c1f087704c24282cebe882268e38146 upstream.
    
    When transitioning from SNK_DEBOUNCED to unattached, its worthwhile to
    check for contaminant to mitigate wakeups.
    
    ```
    [81334.219571] Start toggling
    [81334.228220] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]
    [81334.305147] CC1: 0 -> 0, CC2: 0 -> 3 [state TOGGLING, polarity 0, connected]
    [81334.305162] state change TOGGLING -> SNK_ATTACH_WAIT [rev3 NONE_AMS]
    [81334.305187] pending state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED @ 170 ms [rev3 NONE_AMS]
    [81334.475515] state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED [delayed 170 ms]
    [81334.486480] CC1: 0 -> 0, CC2: 3 -> 0 [state SNK_DEBOUNCED, polarity 0, disconnected]
    [81334.486495] state change SNK_DEBOUNCED -> SNK_DEBOUNCED [rev3 NONE_AMS]
    [81334.486515] pending state change SNK_DEBOUNCED -> SNK_UNATTACHED @ 20 ms [rev3 NONE_AMS]
    [81334.506621] state change SNK_DEBOUNCED -> SNK_UNATTACHED [delayed 20 ms]
    [81334.506640] Start toggling
    [81334.516972] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]
    [81334.592759] CC1: 0 -> 0, CC2: 0 -> 3 [state TOGGLING, polarity 0, connected]
    [81334.592773] state change TOGGLING -> SNK_ATTACH_WAIT [rev3 NONE_AMS]
    [81334.592792] pending state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED @ 170 ms [rev3 NONE_AMS]
    [81334.762940] state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED [delayed 170 ms]
    [81334.773557] CC1: 0 -> 0, CC2: 3 -> 0 [state SNK_DEBOUNCED, polarity 0, disconnected]
    [81334.773570] state change SNK_DEBOUNCED -> SNK_DEBOUNCED [rev3 NONE_AMS]
    [81334.773588] pending state change SNK_DEBOUNCED -> SNK_UNATTACHED @ 20 ms [rev3 NONE_AMS]
    [81334.793672] state change SNK_DEBOUNCED -> SNK_UNATTACHED [delayed 20 ms]
    [81334.793681] Start toggling
    [81334.801840] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]
    [81334.878655] CC1: 0 -> 0, CC2: 0 -> 3 [state TOGGLING, polarity 0, connected]
    [81334.878672] state change TOGGLING -> SNK_ATTACH_WAIT [rev3 NONE_AMS]
    [81334.878696] pending state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED @ 170 ms [rev3 NONE_AMS]
    [81335.048968] state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED [delayed 170 ms]
    [81335.060684] CC1: 0 -> 0, CC2: 3 -> 0 [state SNK_DEBOUNCED, polarity 0, disconnected]
    [81335.060754] state change SNK_DEBOUNCED -> SNK_DEBOUNCED [rev3 NONE_AMS]
    [81335.060775] pending state change SNK_DEBOUNCED -> SNK_UNATTACHED @ 20 ms [rev3 NONE_AMS]
    [81335.080884] state change SNK_DEBOUNCED -> SNK_UNATTACHED [delayed 20 ms]
    [81335.080900] Start toggling
    ```
    
    Cc: stable@vger.kernel.org
    Fixes: 599f008c257d ("usb: typec: tcpm: Add callbacks to mitigate wakeups due to contaminant")
    Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
    Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Link: https://lore.kernel.org/r/20231015053108.2349570-1-badhri@google.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm() [+ + +]
Author: Jimmy Hu <hhhuuu@google.com>
Date:   Fri Oct 20 01:21:32 2023 +0000

    usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm()
    
    commit 4987daf86c152ff882d51572d154ad12e4ff3a4b upstream.
    
    It is possible that typec_register_partner() returns ERR_PTR on failure.
    When port->partner is an error, a NULL pointer dereference may occur as
    shown below.
    
    [91222.095236][  T319] typec port0: failed to register partner (-17)
    ...
    [91225.061491][  T319] Unable to handle kernel NULL pointer dereference
    at virtual address 000000000000039f
    [91225.274642][  T319] pc : tcpm_pd_data_request+0x310/0x13fc
    [91225.274646][  T319] lr : tcpm_pd_data_request+0x298/0x13fc
    [91225.308067][  T319] Call trace:
    [91225.308070][  T319]  tcpm_pd_data_request+0x310/0x13fc
    [91225.308073][  T319]  tcpm_pd_rx_handler+0x100/0x9e8
    [91225.355900][  T319]  kthread_worker_fn+0x178/0x58c
    [91225.355902][  T319]  kthread+0x150/0x200
    [91225.355905][  T319]  ret_from_fork+0x10/0x30
    
    Add a check for port->partner to avoid dereferencing a NULL pointer.
    
    Fixes: 5e1d4c49fbc8 ("usb: typec: tcpm: Determine common SVDM Version")
    Cc: stable@vger.kernel.org
    Signed-off-by: Jimmy Hu <hhhuuu@google.com>
    Link: https://lore.kernel.org/r/20231020012132.100960-1-hhhuuu@google.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
x86/efistub: Don't try to print after ExitBootService() [+ + +]
Author: Nikolay Borisov <nik.borisov@suse.com>
Date:   Wed Oct 11 22:25:28 2023 +0300

    x86/efistub: Don't try to print after ExitBootService()
    
    [ Upstream commit ff07186b4d774ac22a5345d30763045af4569416 ]
    
    setup_e820() is executed after UEFI's ExitBootService has been called.
    This causes the firmware to throw an exception because the Console IO
    protocol is supposed to work only during boot service environment. As
    per UEFI 2.9, section 12.1:
    
     "This protocol is used to handle input and output of text-based
     information intended for the system user during the operation of code
     in the boot services environment."
    
    So drop the diagnostic warning from this function. We might add back a
    warning that is issued later when initializing the kernel itself.
    
    Signed-off-by: Nikolay Borisov <nik.borisov@suse.com>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>