Changelog in Linux kernel 6.6.97

Author: Rafael J. Wysocki <[email protected]>
Date:   Wed Jun 18 14:17:45 2025 +0200

    ACPICA: Refuse to evaluate a method if arguments are missing
    
    [ Upstream commit 6fcab2791543924d438e7fa49276d0998b0a069f ]
    
    As reported in [1], a platform firmware update that increased the number
    of method parameters and forgot to update a least one of its callers,
    caused ACPICA to crash due to use-after-free.
    
    Since this a result of a clear AML issue that arguably cannot be fixed
    up by the interpreter (it cannot produce missing data out of thin air),
    address it by making ACPICA refuse to evaluate a method if the caller
    attempts to pass fewer arguments than expected to it.
    
    Closes: https://github.com/acpica/acpica/issues/1027 [1]
    Reported-by: Peter Williams <[email protected]>
    Signed-off-by: Rafael J. Wysocki <[email protected]>
    Reviewed-by: Hans de Goede <[email protected]>
    Tested-by: Hans de Goede <[email protected]> # Dell XPS 9640 with BIOS 1.12.0
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Rafael J. Wysocki <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Takashi Iwai <[email protected]>
Date:   Tue Jun 10 08:43:19 2025 +0200

    ALSA: sb: Don't allow changing the DMA mode during operations
    
    [ Upstream commit ed29e073ba93f2d52832804cabdd831d5d357d33 ]
    
    When a PCM stream is already running, one shouldn't change the DMA
    mode via kcontrol, which may screw up the hardware.  Return -EBUSY
    instead.
    
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=218185
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Takashi Iwai <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Takashi Iwai <[email protected]>
Date:   Tue Jun 10 08:43:20 2025 +0200

    ALSA: sb: Force to disable DMAs once when DMA mode is changed
    
    [ Upstream commit 4c267ae2ef349639b4d9ebf00dd28586a82fdbe6 ]
    
    When the DMA mode is changed on the (still real!) SB AWE32 after
    playing a stream and closing, the previous DMA setup was still
    silently kept, and it can confuse the hardware, resulting in the
    unexpected noises.  As a workaround, enforce the disablement of DMA
    setups when the DMA setup is changed by the kcontrol.
    
    https://bugzilla.kernel.org/show_bug.cgi?id=218185
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Takashi Iwai <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Raju Rangoju <[email protected]>
Date:   Tue Jul 1 00:56:36 2025 +0530

    amd-xgbe: align CL37 AN sequence as per databook
    
    [ Upstream commit 42fd432fe6d320323215ebdf4de4d0d7e56e6792 ]
    
    Update the Clause 37 Auto-Negotiation implementation to properly align
    with the PCS hardware specifications:
    - Fix incorrect bit settings in Link Status and Link Duplex fields
    - Implement missing sequence steps 2 and 7
    
    These changes ensure CL37 auto-negotiation protocol follows the exact
    sequence patterns as specified in the hardware databook.
    
    Fixes: 1bf40ada6290 ("amd-xgbe: Add support for clause 37 auto-negotiation")
    Signed-off-by: Raju Rangoju <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Raju Rangoju <[email protected]>
Date:   Tue Jul 1 12:20:16 2025 +0530

    amd-xgbe: do not double read link status
    
    [ Upstream commit 16ceda2ef683a50cd0783006c0504e1931cd8879 ]
    
    The link status is latched low so that momentary link drops
    can be detected. Always double-reading the status defeats this
    design feature. Only double read if link was already down
    
    This prevents unnecessary duplicate readings of the link status.
    
    Fixes: 4f3b20bfbb75 ("amd-xgbe: add support for rx-adaptation")
    Signed-off-by: Raju Rangoju <[email protected]>
    Reviewed-by: Simon Horman <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Justin Sanders <[email protected]>
Date:   Tue Jun 10 17:06:00 2025 +0000

    aoe: defer rexmit timer downdev work to workqueue
    
    [ Upstream commit cffc873d68ab09a0432b8212008c5613f8a70a2c ]
    
    When aoe's rexmit_timer() notices that an aoe target fails to respond to
    commands for more than aoe_deadsecs, it calls aoedev_downdev() which
    cleans the outstanding aoe and block queues. This can involve sleeping,
    such as in blk_mq_freeze_queue(), which should not occur in irq context.
    
    This patch defers that aoedev_downdev() call to the aoe device's
    workqueue.
    
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=212665
    Signed-off-by: Justin Sanders <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Tested-By: Valentin Kleibel <[email protected]>
    Signed-off-by: Jens Axboe <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Janne Grunau <[email protected]>
Date:   Wed Jun 11 22:30:31 2025 +0200

    arm64: dts: apple: t8103: Fix PCIe BCM4377 nodename
    
    [ Upstream commit ac1daa91e9370e3b88ef7826a73d62a4d09e2717 ]
    
    Fix the following `make dtbs_check` warnings for all t8103 based devices:
    
    arch/arm64/boot/dts/apple/t8103-j274.dtb: network@0,0: $nodename:0: 'network@0,0' does not match '^wifi(@.*)?$'
            from schema $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
    arch/arm64/boot/dts/apple/t8103-j274.dtb: network@0,0: Unevaluated properties are not allowed ('local-mac-address' was unexpected)
            from schema $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
    
    Fixes: bf2c05b619ff ("arm64: dts: apple: t8103: Expose PCI node for the WiFi MAC address")
    Signed-off-by: Janne Grunau <[email protected]>
    Reviewed-by: Sven Peter <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Sven Peter <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Neil Armstrong <[email protected]>
Date:   Mon Sep 11 09:28:46 2023 +0200

    arm64: dts: qcom: sm8550: add UART14 nodes
    
    [ Upstream commit 75cac7090298978c12c59dbca377d957f6f8a8bb ]
    
    Add the Geni High Speed UART QUP instance 2 element 6
    node and associated default pinctrl.
    
    Reviewed-by: Krzysztof Kozlowski <[email protected]>
    Signed-off-by: Neil Armstrong <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Bjorn Andersson <[email protected]>
    Stable-dep-of: 5ff1fbb30597 ("platform/x86: think-lmi: Fix class device unregistration")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Gabriel Santese <[email protected]>
Date:   Fri May 30 02:52:32 2025 +0200

    ASoC: amd: yc: Add quirk for MSI Bravo 17 D7VF internal mic
    
    [ Upstream commit ba06528ad5a31923efc24324706116ccd17e12d8 ]
    
    MSI Bravo 17 (D7VF), like other laptops from the family,
    has broken ACPI tables and needs a quirk for internal mic
    to work properly.
    
    Signed-off-by: Gabriel Santese <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Mark Brown <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Raven Black <[email protected]>
Date:   Fri Jun 13 07:51:25 2025 -0400

    ASoC: amd: yc: update quirk data for HP Victus
    
    [ Upstream commit 13b86ea92ebf0fa587fbadfb8a60ca2e9993203f ]
    
    Make the internal microphone work on HP Victus laptops.
    
    Signed-off-by: Raven Black <[email protected]>
    Link: https://patch.msgid.link/20250613-support-hp-victus-microphone-v1-1-bebc4c3a2041@gmail.com
    Signed-off-by: Mark Brown <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Tasos Sahanidis <[email protected]>
Date:   Mon May 19 11:56:55 2025 +0300

    ata: libata-acpi: Do not assume 40 wire cable if no devices are enabled
    
    [ Upstream commit 33877220b8641b4cde474a4229ea92c0e3637883 ]
    
    On at least an ASRock 990FX Extreme 4 with a VIA VT6330, the devices
    have not yet been enabled by the first time ata_acpi_cbl_80wire() is
    called. This means that the ata_for_each_dev loop is never entered,
    and a 40 wire cable is assumed.
    
    The VIA controller on this board does not report the cable in the PCI
    config space, thus having to fall back to ACPI even though no SATA
    bridge is present.
    
    The _GTM values are correctly reported by the firmware through ACPI,
    which has already set up faster transfer modes, but due to the above
    the controller is forced down to a maximum of UDMA/33.
    
    Resolve this by modifying ata_acpi_cbl_80wire() to directly return the
    cable type. First, an unknown cable is assumed which preserves the mode
    set by the firmware, and then on subsequent calls when the devices have
    been enabled, an 80 wire cable is correctly detected.
    
    Since the function now directly returns the cable type, it is renamed
    to ata_acpi_cbl_pata_type().
    
    Signed-off-by: Tasos Sahanidis <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Niklas Cassel <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Johannes Berg <[email protected]>
Date:   Fri Jun 6 11:01:11 2025 +0200

    ata: pata_cs5536: fix build on 32-bit UML
    
    [ Upstream commit fe5b391fc56f77cf3c22a9dd4f0ce20db0e3533f ]
    
    On 32-bit ARCH=um, CONFIG_X86_32 is still defined, so it
    doesn't indicate building on real X86 machines. There's
    no MSR on UML though, so add a check for CONFIG_X86.
    
    Reported-by: Arnd Bergmann <[email protected]>
    Signed-off-by: Johannes Berg <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Niklas Cassel <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kuniyuki Iwashima <[email protected]>
Date:   Sun Jul 6 05:34:31 2025 -0400

    Bluetooth: hci_core: Fix use-after-free in vhci_flush()
    
    [ Upstream commit 1d6123102e9fbedc8d25bf4731da6d513173e49e ]
    
    syzbot reported use-after-free in vhci_flush() without repro. [0]
    
    From the splat, a thread close()d a vhci file descriptor while
    its device was being used by iotcl() on another thread.
    
    Once the last fd refcnt is released, vhci_release() calls
    hci_unregister_dev(), hci_free_dev(), and kfree() for struct
    vhci_data, which is set to hci_dev->dev->driver_data.
    
    The problem is that there is no synchronisation after unlinking
    hdev from hci_dev_list in hci_unregister_dev().  There might be
    another thread still accessing the hdev which was fetched before
    the unlink operation.
    
    We can use SRCU for such synchronisation.
    
    Let's run hci_dev_reset() under SRCU and wait for its completion
    in hci_unregister_dev().
    
    Another option would be to restore hci_dev->destruct(), which was
    removed in commit 587ae086f6e4 ("Bluetooth: Remove unused
    hci-destruct cb").  However, this would not be a good solution, as
    we should not run hci_unregister_dev() while there are in-flight
    ioctl() requests, which could lead to another data-race KCSAN splat.
    
    Note that other drivers seem to have the same problem, for exmaple,
    virtbt_remove().
    
    [0]:
    BUG: KASAN: slab-use-after-free in skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline]
    BUG: KASAN: slab-use-after-free in skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937
    Read of size 8 at addr ffff88807cb8d858 by task syz.1.219/6718
    
    CPU: 1 UID: 0 PID: 6718 Comm: syz.1.219 Not tainted 6.16.0-rc1-syzkaller-00196-g08207f42d3ff #0 PREEMPT(full)
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
    Call Trace:
     <TASK>
     dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
     print_address_description mm/kasan/report.c:408 [inline]
     print_report+0xd2/0x2b0 mm/kasan/report.c:521
     kasan_report+0x118/0x150 mm/kasan/report.c:634
     skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline]
     skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937
     skb_queue_purge include/linux/skbuff.h:3368 [inline]
     vhci_flush+0x44/0x50 drivers/bluetooth/hci_vhci.c:69
     hci_dev_do_reset net/bluetooth/hci_core.c:552 [inline]
     hci_dev_reset+0x420/0x5c0 net/bluetooth/hci_core.c:592
     sock_do_ioctl+0xd9/0x300 net/socket.c:1190
     sock_ioctl+0x576/0x790 net/socket.c:1311
     vfs_ioctl fs/ioctl.c:51 [inline]
     __do_sys_ioctl fs/ioctl.c:907 [inline]
     __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893
     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
     entry_SYSCALL_64_after_hwframe+0x77/0x7f
    RIP: 0033:0x7fcf5b98e929
    Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
    RSP: 002b:00007fcf5c7b9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
    RAX: ffffffffffffffda RBX: 00007fcf5bbb6160 RCX: 00007fcf5b98e929
    RDX: 0000000000000000 RSI: 00000000400448cb RDI: 0000000000000009
    RBP: 00007fcf5ba10b39 R08: 0000000000000000 R09: 0000000000000000
    R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
    R13: 0000000000000000 R14: 00007fcf5bbb6160 R15: 00007ffd6353d528
     </TASK>
    
    Allocated by task 6535:
     kasan_save_stack mm/kasan/common.c:47 [inline]
     kasan_save_track+0x3e/0x80 mm/kasan/common.c:68
     poison_kmalloc_redzone mm/kasan/common.c:377 [inline]
     __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394
     kasan_kmalloc include/linux/kasan.h:260 [inline]
     __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4359
     kmalloc_noprof include/linux/slab.h:905 [inline]
     kzalloc_noprof include/linux/slab.h:1039 [inline]
     vhci_open+0x57/0x360 drivers/bluetooth/hci_vhci.c:635
     misc_open+0x2bc/0x330 drivers/char/misc.c:161
     chrdev_open+0x4c9/0x5e0 fs/char_dev.c:414
     do_dentry_open+0xdf0/0x1970 fs/open.c:964
     vfs_open+0x3b/0x340 fs/open.c:1094
     do_open fs/namei.c:3887 [inline]
     path_openat+0x2ee5/0x3830 fs/namei.c:4046
     do_filp_open+0x1fa/0x410 fs/namei.c:4073
     do_sys_openat2+0x121/0x1c0 fs/open.c:1437
     do_sys_open fs/open.c:1452 [inline]
     __do_sys_openat fs/open.c:1468 [inline]
     __se_sys_openat fs/open.c:1463 [inline]
     __x64_sys_openat+0x138/0x170 fs/open.c:1463
     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
     entry_SYSCALL_64_after_hwframe+0x77/0x7f
    
    Freed by task 6535:
     kasan_save_stack mm/kasan/common.c:47 [inline]
     kasan_save_track+0x3e/0x80 mm/kasan/common.c:68
     kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576
     poison_slab_object mm/kasan/common.c:247 [inline]
     __kasan_slab_free+0x62/0x70 mm/kasan/common.c:264
     kasan_slab_free include/linux/kasan.h:233 [inline]
     slab_free_hook mm/slub.c:2381 [inline]
     slab_free mm/slub.c:4643 [inline]
     kfree+0x18e/0x440 mm/slub.c:4842
     vhci_release+0xbc/0xd0 drivers/bluetooth/hci_vhci.c:671
     __fput+0x44c/0xa70 fs/file_table.c:465
     task_work_run+0x1d1/0x260 kernel/task_work.c:227
     exit_task_work include/linux/task_work.h:40 [inline]
     do_exit+0x6ad/0x22e0 kernel/exit.c:955
     do_group_exit+0x21c/0x2d0 kernel/exit.c:1104
     __do_sys_exit_group kernel/exit.c:1115 [inline]
     __se_sys_exit_group kernel/exit.c:1113 [inline]
     __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1113
     x64_sys_call+0x21ba/0x21c0 arch/x86/include/generated/asm/syscalls_64.h:232
     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
     entry_SYSCALL_64_after_hwframe+0x77/0x7f
    
    The buggy address belongs to the object at ffff88807cb8d800
     which belongs to the cache kmalloc-1k of size 1024
    The buggy address is located 88 bytes inside of
     freed 1024-byte region [ffff88807cb8d800, ffff88807cb8dc00)
    
    Fixes: bf18c7118cf8 ("Bluetooth: vhci: Free driver_data on file release")
    Reported-by: [email protected]
    Closes: https://syzkaller.appspot.com/bug?extid=f62d64848fc4c7c30cd6
    Signed-off-by: Kuniyuki Iwashima <[email protected]>
    Acked-by: Paul Menzel <[email protected]>
    Signed-off-by: Luiz Augusto von Dentz <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Christian Eggers <[email protected]>
Date:   Wed Jun 25 15:09:29 2025 +0200

    Bluetooth: hci_sync: revert some mesh modifications
    
    commit 46c0d947b64ac8efcf89dd754213dab5d1bd00aa upstream.
    
    This reverts minor parts of the changes made in commit b338d91703fa
    ("Bluetooth: Implement support for Mesh"). It looks like these changes
    were only made for development purposes but shouldn't have been part of
    the commit.
    
    Fixes: b338d91703fa ("Bluetooth: Implement support for Mesh")
    Cc: [email protected]
    Signed-off-by: Christian Eggers <[email protected]>
    Signed-off-by: Luiz Augusto von Dentz <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Christian Eggers <[email protected]>
Date:   Wed Jun 25 15:09:31 2025 +0200

    Bluetooth: MGMT: mesh_send: check instances prior disabling advertising
    
    commit f3cb5676e5c11c896ba647ee309a993e73531588 upstream.
    
    The unconditional call of hci_disable_advertising_sync() in
    mesh_send_done_sync() also disables other LE advertisings (non mesh
    related).
    
    I am not sure whether this call is required at all, but checking the
    adv_instances list (like done at other places) seems to solve the
    problem.
    
    Fixes: b338d91703fa ("Bluetooth: Implement support for Mesh")
    Cc: [email protected]
    Signed-off-by: Christian Eggers <[email protected]>
    Signed-off-by: Luiz Augusto von Dentz <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Christian Eggers <[email protected]>
Date:   Wed Jun 25 15:09:30 2025 +0200

    Bluetooth: MGMT: set_mesh: update LE scan interval and window
    
    commit e5af67a870f738bb8a4594b6c60c2caf4c87a3c9 upstream.
    
    According to the message of commit b338d91703fa ("Bluetooth: Implement
    support for Mesh"), MGMT_OP_SET_MESH_RECEIVER should set the passive scan
    parameters.  Currently the scan interval and window parameters are
    silently ignored, although user space (bluetooth-meshd) expects that
    they can be used [1]
    
    [1] https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/mesh/mesh-io-mgmt.c#n344
    Fixes: b338d91703fa ("Bluetooth: Implement support for Mesh")
    Cc: [email protected]
    Signed-off-by: Christian Eggers <[email protected]>
    Signed-off-by: Luiz Augusto von Dentz <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Yang Li <[email protected]>
Date:   Thu Jun 19 11:01:07 2025 +0800

    Bluetooth: Prevent unintended pause by checking if advertising is active
    
    [ Upstream commit 1f029b4e30a602db33dedee5ac676e9236ad193c ]
    
    When PA Create Sync is enabled, advertising resumes unexpectedly.
    Therefore, it's necessary to check whether advertising is currently
    active before attempting to pause it.
    
      < HCI Command: LE Add Device To... (0x08|0x0011) plen 7  #1345 [hci0] 48.306205
                    Address type: Random (0x01)
                    Address: 4F:84:84:5F:88:17 (Resolvable)
                    Identity type: Random (0x01)
                    Identity: FC:5B:8C:F7:5D:FB (Static)
      < HCI Command: LE Set Address Re.. (0x08|0x002d) plen 1  #1347 [hci0] 48.308023
                    Address resolution: Enabled (0x01)
      ...
      < HCI Command: LE Set Extended A.. (0x08|0x0039) plen 6  #1349 [hci0] 48.309650
                    Extended advertising: Enabled (0x01)
                    Number of sets: 1 (0x01)
                    Entry 0
                    Handle: 0x01
                    Duration: 0 ms (0x00)
                    Max ext adv events: 0
      ...
      < HCI Command: LE Periodic Adve.. (0x08|0x0044) plen 14  #1355 [hci0] 48.314575
                    Options: 0x0000
                    Use advertising SID, Advertiser Address Type and address
                    Reporting initially enabled
                    SID: 0x02
                    Adv address type: Random (0x01)
                    Adv address: 4F:84:84:5F:88:17 (Resolvable)
                    Identity type: Random (0x01)
                    Identity: FC:5B:8C:F7:5D:FB (Static)
                    Skip: 0x0000
                    Sync timeout: 20000 msec (0x07d0)
                    Sync CTE type: 0x0000
    
    Fixes: ad383c2c65a5 ("Bluetooth: hci_sync: Enable advertising when LL privacy is enabled")
    Signed-off-by: Yang Li <[email protected]>
    Signed-off-by: Luiz Augusto von Dentz <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Yan Zhai <[email protected]>
Date:   Mon Jun 23 09:06:38 2025 -0700

    bnxt: properly flush XDP redirect lists
    
    [ Upstream commit 9caca6ac0e26cd20efd490d8b3b2ffb1c7c00f6f ]
    
    We encountered following crash when testing a XDP_REDIRECT feature
    in production:
    
    [56251.579676] list_add corruption. next->prev should be prev (ffff93120dd40f30), but was ffffb301ef3a6740. (next=ffff93120dd
    40f30).
    [56251.601413] ------------[ cut here ]------------
    [56251.611357] kernel BUG at lib/list_debug.c:29!
    [56251.621082] Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
    [56251.632073] CPU: 111 UID: 0 PID: 0 Comm: swapper/111 Kdump: loaded Tainted: P           O       6.12.33-cloudflare-2025.6.
    3 #1
    [56251.653155] Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE
    [56251.663877] Hardware name: MiTAC GC68B-B8032-G11P6-GPU/S8032GM-HE-CFR, BIOS V7.020.B10-sig 01/22/2025
    [56251.682626] RIP: 0010:__list_add_valid_or_report+0x4b/0xa0
    [56251.693203] Code: 0e 48 c7 c7 68 e7 d9 97 e8 42 16 fe ff 0f 0b 48 8b 52 08 48 39 c2 74 14 48 89 f1 48 c7 c7 90 e7 d9 97 48
     89 c6 e8 25 16 fe ff <0f> 0b 4c 8b 02 49 39 f0 74 14 48 89 d1 48 c7 c7 e8 e7 d9 97 4c 89
    [56251.725811] RSP: 0018:ffff93120dd40b80 EFLAGS: 00010246
    [56251.736094] RAX: 0000000000000075 RBX: ffffb301e6bba9d8 RCX: 0000000000000000
    [56251.748260] RDX: 0000000000000000 RSI: ffff9149afda0b80 RDI: ffff9149afda0b80
    [56251.760349] RBP: ffff9131e49c8000 R08: 0000000000000000 R09: ffff93120dd40a18
    [56251.772382] R10: ffff9159cf2ce1a8 R11: 0000000000000003 R12: ffff911a80850000
    [56251.784364] R13: ffff93120fbc7000 R14: 0000000000000010 R15: ffff9139e7510e40
    [56251.796278] FS:  0000000000000000(0000) GS:ffff9149afd80000(0000) knlGS:0000000000000000
    [56251.809133] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [56251.819561] CR2: 00007f5e85e6f300 CR3: 00000038b85e2006 CR4: 0000000000770ef0
    [56251.831365] PKRU: 55555554
    [56251.838653] Call Trace:
    [56251.845560]  <IRQ>
    [56251.851943]  cpu_map_enqueue.cold+0x5/0xa
    [56251.860243]  xdp_do_redirect+0x2d9/0x480
    [56251.868388]  bnxt_rx_xdp+0x1d8/0x4c0 [bnxt_en]
    [56251.877028]  bnxt_rx_pkt+0x5f7/0x19b0 [bnxt_en]
    [56251.885665]  ? cpu_max_write+0x1e/0x100
    [56251.893510]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56251.902276]  __bnxt_poll_work+0x190/0x340 [bnxt_en]
    [56251.911058]  bnxt_poll+0xab/0x1b0 [bnxt_en]
    [56251.919041]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56251.927568]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56251.935958]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56251.944250]  __napi_poll+0x2b/0x160
    [56251.951155]  bpf_trampoline_6442548651+0x79/0x123
    [56251.959262]  __napi_poll+0x5/0x160
    [56251.966037]  net_rx_action+0x3d2/0x880
    [56251.973133]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56251.981265]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56251.989262]  ? __hrtimer_run_queues+0x162/0x2a0
    [56251.996967]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56252.004875]  ? srso_alias_return_thunk+0x5/0xfbef5
    [56252.012673]  ? bnxt_msix+0x62/0x70 [bnxt_en]
    [56252.019903]  handle_softirqs+0xcf/0x270
    [56252.026650]  irq_exit_rcu+0x67/0x90
    [56252.032933]  common_interrupt+0x85/0xa0
    [56252.039498]  </IRQ>
    [56252.044246]  <TASK>
    [56252.048935]  asm_common_interrupt+0x26/0x40
    [56252.055727] RIP: 0010:cpuidle_enter_state+0xb8/0x420
    [56252.063305] Code: dc 01 00 00 e8 f9 79 3b ff e8 64 f7 ff ff 49 89 c5 0f 1f 44 00 00 31 ff e8 a5 32 3a ff 45 84 ff 0f 85 ae
     01 00 00 fb 45 85 f6 <0f> 88 88 01 00 00 48 8b 04 24 49 63 ce 4c 89 ea 48 6b f1 68 48 29
    [56252.088911] RSP: 0018:ffff93120c97fe98 EFLAGS: 00000202
    [56252.096912] RAX: ffff9149afd80000 RBX: ffff9141d3a72800 RCX: 0000000000000000
    [56252.106844] RDX: 00003329176c6b98 RSI: ffffffe36db3fdc7 RDI: 0000000000000000
    [56252.116733] RBP: 0000000000000002 R08: 0000000000000002 R09: 000000000000004e
    [56252.126652] R10: ffff9149afdb30c4 R11: 071c71c71c71c71c R12: ffffffff985ff860
    [56252.136637] R13: 00003329176c6b98 R14: 0000000000000002 R15: 0000000000000000
    [56252.146667]  ? cpuidle_enter_state+0xab/0x420
    [56252.153909]  cpuidle_enter+0x2d/0x40
    [56252.160360]  do_idle+0x176/0x1c0
    [56252.166456]  cpu_startup_entry+0x29/0x30
    [56252.173248]  start_secondary+0xf7/0x100
    [56252.179941]  common_startup_64+0x13e/0x141
    [56252.186886]  </TASK>
    
    From the crash dump, we found that the cpu_map_flush_list inside
    redirect info is partially corrupted: its list_head->next points to
    itself, but list_head->prev points to a valid list of unflushed bq
    entries.
    
    This turned out to be a result of missed XDP flush on redirect lists. By
    digging in the actual source code, we found that
    commit 7f0a168b0441 ("bnxt_en: Add completion ring pointer in TX and RX
    ring structures") incorrectly overwrites the event mask for XDP_REDIRECT
    in bnxt_rx_xdp. We can stably reproduce this crash by returning XDP_TX
    and XDP_REDIRECT randomly for incoming packets in a naive XDP program.
    Properly propagate the XDP_REDIRECT events back fixes the crash.
    
    Fixes: a7559bc8c17c ("bnxt: support transmit and free of aggregation buffers")
    Tested-by: Andrew Rzeznik <[email protected]>
    Signed-off-by: Yan Zhai <[email protected]>
    Acked-by: Jesper Dangaard Brouer <[email protected]>
    Reviewed-by: Michael Chan <[email protected]>
    Reviewed-by: Andy Gospodarek <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Filipe Manana <[email protected]>
Date:   Mon Jun 23 12:11:58 2025 +0100

    btrfs: fix iteration of extrefs during log replay
    
    [ Upstream commit 54a7081ed168b72a8a2d6ef4ba3a1259705a2926 ]
    
    At __inode_add_ref() when processing extrefs, if we jump into the next
    label we have an undefined value of victim_name.len, since we haven't
    initialized it before we did the goto. This results in an invalid memory
    access in the next iteration of the loop since victim_name.len was not
    initialized to the length of the name of the current extref.
    
    Fix this by initializing victim_name.len with the current extref's name
    length.
    
    Fixes: e43eec81c516 ("btrfs: use struct qstr instead of name and namelen pairs")
    Reviewed-by: Johannes Thumshirn <[email protected]>
    Reviewed-by: Qu Wenruo <[email protected]>
    Signed-off-by: Filipe Manana <[email protected]>
    Signed-off-by: David Sterba <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Filipe Manana <[email protected]>
Date:   Wed Jun 18 16:57:07 2025 +0100

    btrfs: fix missing error handling when searching for inode refs during log replay
    
    [ Upstream commit 6561a40ceced9082f50c374a22d5966cf9fc5f5c ]
    
    During log replay, at __add_inode_ref(), when we are searching for inode
    ref keys we totally ignore if btrfs_search_slot() returns an error. This
    may make a log replay succeed when there was an actual error and leave
    some metadata inconsistency in a subvolume tree. Fix this by checking if
    an error was returned from btrfs_search_slot() and if so, return it to
    the caller.
    
    Fixes: e02119d5a7b4 ("Btrfs: Add a write ahead tree log to optimize synchronous operations")
    Reviewed-by: Johannes Thumshirn <[email protected]>
    Reviewed-by: Qu Wenruo <[email protected]>
    Signed-off-by: Filipe Manana <[email protected]>
    Signed-off-by: David Sterba <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Filipe Manana <[email protected]>
Date:   Wed May 7 13:05:36 2025 +0100

    btrfs: fix qgroup reservation leak on failure to allocate ordered extent
    
    [ Upstream commit 1f2889f5594a2bc4c6a52634c4a51b93e785def5 ]
    
    If we fail to allocate an ordered extent for a COW write we end up leaking
    a qgroup data reservation since we called btrfs_qgroup_release_data() but
    we didn't call btrfs_qgroup_free_refroot() (which would happen when
    running the respective data delayed ref created by ordered extent
    completion or when finishing the ordered extent in case an error happened).
    
    So make sure we call btrfs_qgroup_free_refroot() if we fail to allocate an
    ordered extent for a COW write.
    
    Fixes: 7dbeaad0af7d ("btrfs: change timing for qgroup reserved space for ordered extents to fix reserved space leak")
    CC: [email protected] # 6.1+
    Reviewed-by: Boris Burkov <[email protected]>
    Reviewed-by: Qu Wenruo <[email protected]>
    Signed-off-by: Filipe Manana <[email protected]>
    Signed-off-by: David Sterba <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Filipe Manana <[email protected]>
Date:   Fri Jun 20 15:54:05 2025 +0100

    btrfs: propagate last_unlink_trans earlier when doing a rmdir
    
    [ Upstream commit c466e33e729a0ee017d10d919cba18f503853c60 ]
    
    In case the removed directory had a snapshot that was deleted, we are
    propagating its inode's last_unlink_trans to the parent directory after
    we removed the entry from the parent directory. This leaves a small race
    window where someone can log the parent directory after we removed the
    entry and before we updated last_unlink_trans, and as a result if we ever
    try to replay such a log tree, we will fail since we will attempt to
    remove a snapshot during log replay, which is currently not possible and
    results in the log replay (and mount) to fail. This is the type of failure
    described in commit 1ec9a1ae1e30 ("Btrfs: fix unreplayable log after
    snapshot delete + parent dir fsync").
    
    So fix this by propagating the last_unlink_trans to the parent directory
    before we remove the entry from it.
    
    Fixes: 44f714dae50a ("Btrfs: improve performance on fsync against new inode after rename/unlink")
    Reviewed-by: Johannes Thumshirn <[email protected]>
    Signed-off-by: Filipe Manana <[email protected]>
    Signed-off-by: David Sterba <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Anand Jain <[email protected]>
Date:   Tue Mar 19 11:40:23 2024 +0800

    btrfs: rename err to ret in btrfs_rmdir()
    
    [ Upstream commit c3a1cc8ff48875b050fda5285ac8a9889eb7898d ]
    
    Unify naming of return value to the preferred way.
    
    Signed-off-by: Anand Jain <[email protected]>
    Reviewed-by: David Sterba <[email protected]>
    Signed-off-by: David Sterba <[email protected]>
    Stable-dep-of: c466e33e729a ("btrfs: propagate last_unlink_trans earlier when doing a rmdir")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Filipe Manana <[email protected]>
Date:   Fri Jun 20 16:37:01 2025 +0100

    btrfs: use btrfs_record_snapshot_destroy() during rmdir
    
    [ Upstream commit 157501b0469969fc1ba53add5049575aadd79d80 ]
    
    We are setting the parent directory's last_unlink_trans directly which
    may result in a concurrent task starting to log the directory not see the
    update and therefore can log the directory after we removed a child
    directory which had a snapshot within instead of falling back to a
    transaction commit. Replaying such a log tree would result in a mount
    failure since we can't currently delete snapshots (and subvolumes) during
    log replay. This is the type of failure described in commit 1ec9a1ae1e30
    ("Btrfs: fix unreplayable log after snapshot delete + parent dir fsync").
    
    Fix this by using btrfs_record_snapshot_destroy() which updates the
    last_unlink_trans field while holding the inode's log_mutex lock.
    
    Fixes: 44f714dae50a ("Btrfs: improve performance on fsync against new inode after rename/unlink")
    Reviewed-by: Johannes Thumshirn <[email protected]>
    Signed-off-by: Filipe Manana <[email protected]>
    Signed-off-by: David Sterba <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Christian König <[email protected]>
Date:   Tue Jan 28 10:47:48 2025 +0100

    dma-buf: fix timeout handling in dma_resv_wait_timeout v2
    
    commit 2b95a7db6e0f75587bffddbb490399cbb87e4985 upstream.
    
    Even the kerneldoc says that with a zero timeout the function should not
    wait for anything, but still return 1 to indicate that the fences are
    signaled now.
    
    Unfortunately that isn't what was implemented, instead of only returning
    1 we also waited for at least one jiffies.
    
    Fix that by adjusting the handling to what the function is actually
    documented to do.
    
    v2: improve code readability
    
    Reported-by: Marek Olšák <[email protected]>
    Reported-by: Lucas Stach <[email protected]>
    Signed-off-by: Christian König <[email protected]>
    Reviewed-by: Lucas Stach <[email protected]>
    Cc: <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Fushuai Wang <[email protected]>
Date:   Thu Jun 26 21:30:03 2025 +0800

    dpaa2-eth: fix xdp_rxq_info leak
    
    [ Upstream commit 2def09ead4ad5907988b655d1e1454003aaf8297 ]
    
    The driver registered xdp_rxq_info structures via xdp_rxq_info_reg()
    but failed to properly unregister them in error paths and during
    removal.
    
    Fixes: d678be1dc1ec ("dpaa2-eth: add XDP_REDIRECT support")
    Signed-off-by: Fushuai Wang <[email protected]>
    Reviewed-by: Simon Horman <[email protected]>
    Reviewed-by: Ioana Ciornei <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Marek Szyprowski <[email protected]>
Date:   Wed Jun 18 14:06:26 2025 +0200

    drm/exynos: fimd: Guard display clock control with runtime PM calls
    
    [ Upstream commit 5d91394f236167ac624b823820faf4aa928b889e ]
    
    Commit c9b1150a68d9 ("drm/atomic-helper: Re-order bridge chain pre-enable
    and post-disable") changed the call sequence to the CRTC enable/disable
    and bridge pre_enable/post_disable methods, so those bridge methods are
    now called when CRTC is not yet enabled.
    
    This causes a lockup observed on Samsung Peach-Pit/Pi Chromebooks. The
    source of this lockup is a call to fimd_dp_clock_enable() function, when
    FIMD device is not yet runtime resumed. It worked before the mentioned
    commit only because the CRTC implemented by the FIMD driver was always
    enabled what guaranteed the FIMD device to be runtime resumed.
    
    This patch adds runtime PM guards to the fimd_dp_clock_enable() function
    to enable its proper operation also when the CRTC implemented by FIMD is
    not yet enabled.
    
    Fixes: 196e059a8a6a ("drm/exynos: convert clock_enable crtc callback to pipeline clock")
    Signed-off-by: Marek Szyprowski <[email protected]>
    Reviewed-by: Tomi Valkeinen <[email protected]>
    Signed-off-by: Inki Dae <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Xin Li (Intel) <[email protected]>
Date:   Fri Jun 20 16:15:03 2025 -0700

    drm/i915/dp_mst: Work around Thunderbolt sink disconnect after SINK_COUNT_ESI read
    
    [ Upstream commit 9cb15478916e849d62a6ec44b10c593b9663328c ]
    
    Due to a problem in the iTBT DP-in adapter's firmware the sink on a TBT
    link may get disconnected inadvertently if the SINK_COUNT_ESI and the
    DP_LINK_SERVICE_IRQ_VECTOR_ESI0 registers are read in a single AUX
    transaction. Work around the issue by reading these registers in
    separate transactions.
    
    The issue affects MTL+ platforms and will be fixed in the DP-in adapter
    firmware, however releasing that firmware fix may take some time and is
    not guaranteed to be available for all systems. Based on this apply the
    workaround on affected platforms.
    
    See HSD #13013007775.
    
    v2: Cc'ing Mika Westerberg.
    
    Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13760
    Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14147
    Cc: Mika Westerberg <[email protected]>
    Cc: [email protected]
    Reviewed-by: Mika Westerberg <[email protected]>
    Signed-off-by: Imre Deak <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    (cherry picked from commit c3a48363cf1f76147088b1adb518136ac5df86a0)
    Signed-off-by: Joonas Lahtinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Junxiao Chang <[email protected]>
Date:   Fri Apr 25 23:11:07 2025 +0800

    drm/i915/gsc: mei interrupt top half should be in irq disabled context
    
    [ Upstream commit 8cadce97bf264ed478669c6f32d5603b34608335 ]
    
    MEI GSC interrupt comes from i915. It has top half and bottom half.
    Top half is called from i915 interrupt handler. It should be in
    irq disabled context.
    
    With RT kernel, by default i915 IRQ handler is in threaded IRQ. MEI GSC
    top half might be in threaded IRQ context. generic_handle_irq_safe API
    could be called from either IRQ or process context, it disables local
    IRQ then calls MEI GSC interrupt top half.
    
    This change fixes A380/A770 GPU boot hang issue with RT kernel.
    
    Fixes: 1e3dc1d8622b ("drm/i915/gsc: add gsc as a mei auxiliary device")
    Tested-by: Furong Zhou <[email protected]>
    Suggested-by: Sebastian Andrzej Siewior <[email protected]>
    Acked-by: Sebastian Andrzej Siewior <[email protected]>
    Signed-off-by: Junxiao Chang <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Rodrigo Vivi <[email protected]>
    Signed-off-by: Rodrigo Vivi <[email protected]>
    (cherry picked from commit dccf655f69002d496a527ba441b4f008aa5bebbf)
    Signed-off-by: Joonas Lahtinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Janusz Krzysztofik <[email protected]>
Date:   Wed Jun 11 12:42:13 2025 +0200

    drm/i915/gt: Fix timeline left held on VMA alloc error
    
    [ Upstream commit a5aa7bc1fca78c7fa127d9e33aa94a0c9066c1d6 ]
    
    The following error has been reported sporadically by CI when a test
    unbinds the i915 driver on a ring submission platform:
    
    <4> [239.330153] ------------[ cut here ]------------
    <4> [239.330166] i915 0000:00:02.0: [drm] drm_WARN_ON(dev_priv->mm.shrink_count)
    <4> [239.330196] WARNING: CPU: 1 PID: 18570 at drivers/gpu/drm/i915/i915_gem.c:1309 i915_gem_cleanup_early+0x13e/0x150 [i915]
    ...
    <4> [239.330640] RIP: 0010:i915_gem_cleanup_early+0x13e/0x150 [i915]
    ...
    <4> [239.330942] Call Trace:
    <4> [239.330944]  <TASK>
    <4> [239.330949]  i915_driver_late_release+0x2b/0xa0 [i915]
    <4> [239.331202]  i915_driver_release+0x86/0xa0 [i915]
    <4> [239.331482]  devm_drm_dev_init_release+0x61/0x90
    <4> [239.331494]  devm_action_release+0x15/0x30
    <4> [239.331504]  release_nodes+0x3d/0x120
    <4> [239.331517]  devres_release_all+0x96/0xd0
    <4> [239.331533]  device_unbind_cleanup+0x12/0x80
    <4> [239.331543]  device_release_driver_internal+0x23a/0x280
    <4> [239.331550]  ? bus_find_device+0xa5/0xe0
    <4> [239.331563]  device_driver_detach+0x14/0x20
    ...
    <4> [357.719679] ---[ end trace 0000000000000000 ]---
    
    If the test also unloads the i915 module then that's followed with:
    
    <3> [357.787478] =============================================================================
    <3> [357.788006] BUG i915_vma (Tainted: G     U  W        N ): Objects remaining on __kmem_cache_shutdown()
    <3> [357.788031] -----------------------------------------------------------------------------
    <3> [357.788204] Object 0xffff888109e7f480 @offset=29824
    <3> [357.788670] Allocated in i915_vma_instance+0xee/0xc10 [i915] age=292729 cpu=4 pid=2244
    <4> [357.788994]  i915_vma_instance+0xee/0xc10 [i915]
    <4> [357.789290]  init_status_page+0x7b/0x420 [i915]
    <4> [357.789532]  intel_engines_init+0x1d8/0x980 [i915]
    <4> [357.789772]  intel_gt_init+0x175/0x450 [i915]
    <4> [357.790014]  i915_gem_init+0x113/0x340 [i915]
    <4> [357.790281]  i915_driver_probe+0x847/0xed0 [i915]
    <4> [357.790504]  i915_pci_probe+0xe6/0x220 [i915]
    ...
    
    Closer analysis of CI results history has revealed a dependency of the
    error on a few IGT tests, namely:
    - igt@api_intel_allocator@fork-simple-stress-signal,
    - igt@api_intel_allocator@two-level-inception-interruptible,
    - igt@gem_linear_blits@interruptible,
    - igt@prime_mmap_coherency@ioctl-errors,
    which invisibly trigger the issue, then exhibited with first driver unbind
    attempt.
    
    All of the above tests perform actions which are actively interrupted with
    signals.  Further debugging has allowed to narrow that scope down to
    DRM_IOCTL_I915_GEM_EXECBUFFER2, and ring_context_alloc(), specific to ring
    submission, in particular.
    
    If successful then that function, or its execlists or GuC submission
    equivalent, is supposed to be called only once per GEM context engine,
    followed by raise of a flag that prevents the function from being called
    again.  The function is expected to unwind its internal errors itself, so
    it may be safely called once more after it returns an error.
    
    In case of ring submission, the function first gets a reference to the
    engine's legacy timeline and then allocates a VMA.  If the VMA allocation
    fails, e.g. when i915_vma_instance() called from inside is interrupted
    with a signal, then ring_context_alloc() fails, leaving the timeline held
    referenced.  On next I915_GEM_EXECBUFFER2 IOCTL, another reference to the
    timeline is got, and only that last one is put on successful completion.
    As a consequence, the legacy timeline, with its underlying engine status
    page's VMA object, is still held and not released on driver unbind.
    
    Get the legacy timeline only after successful allocation of the context
    engine's VMA.
    
    v2: Add a note on other submission methods (Krzysztof Karas):
        Both execlists and GuC submission use lrc_alloc() which seems free
        from a similar issue.
    
    Fixes: 75d0a7f31eec ("drm/i915: Lift timeline into intel_context")
    Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
    Cc: Chris Wilson <[email protected]>
    Cc: Matthew Auld <[email protected]>
    Cc: Krzysztof Karas <[email protected]>
    Reviewed-by: Sebastian Brzezinka <[email protected]>
    Reviewed-by: Krzysztof Niemiec <[email protected]>
    Signed-off-by: Janusz Krzysztofik <[email protected]>
    Reviewed-by: Nitin Gote <[email protected]>
    Reviewed-by: Andi Shyti <[email protected]>
    Signed-off-by: Andi Shyti <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    (cherry picked from commit cc43422b3cc79eacff4c5a8ba0d224688ca9dd4f)
    Signed-off-by: Joonas Lahtinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Dan Carpenter <[email protected]>
Date:   Wed Jun 25 10:21:58 2025 -0500

    drm/i915/selftests: Change mock_request() to return error pointers
    
    [ Upstream commit caa7c7a76b78ce41d347003f84975125383e6b59 ]
    
    There was an error pointer vs NULL bug in __igt_breadcrumbs_smoketest().
    The __mock_request_alloc() function implements the
    smoketest->request_alloc() function pointer.  It was supposed to return
    error pointers, but it propogates the NULL return from mock_request()
    so in the event of a failure, it would lead to a NULL pointer
    dereference.
    
    To fix this, change the mock_request() function to return error pointers
    and update all the callers to expect that.
    
    Fixes: 52c0fdb25c7c ("drm/i915: Replace global breadcrumbs with per-context interrupt tracking")
    Signed-off-by: Dan Carpenter <[email protected]>
    Reviewed-by: Rodrigo Vivi <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Rodrigo Vivi <[email protected]>
    (cherry picked from commit 778fa8ad5f0f23397d045c7ebca048ce8def1c43)
    Signed-off-by: Joonas Lahtinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Rob Clark <[email protected]>
Date:   Wed May 14 09:33:32 2025 -0700

    drm/msm: Fix a fence leak in submit error path
    
    [ Upstream commit 5d319f75ccf7f0927425a7545aa1a22b3eedc189 ]
    
    In error paths, we could unref the submit without calling
    drm_sched_entity_push_job(), so msm_job_free() will never get
    called.  Since drm_sched_job_cleanup() will NULL out the
    s_fence, we can use that to detect this case.
    
    Signed-off-by: Rob Clark <[email protected]>
    Patchwork: https://patchwork.freedesktop.org/patch/653584/
    Signed-off-by: Rob Clark <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Rob Clark <[email protected]>
Date:   Wed May 14 09:33:33 2025 -0700

    drm/msm: Fix another leak in the submit error path
    
    [ Upstream commit f681c2aa8676a890eacc84044717ab0fd26e058f ]
    
    put_unused_fd() doesn't free the installed file, if we've already done
    fd_install().  So we need to also free the sync_file.
    
    Signed-off-by: Rob Clark <[email protected]>
    Patchwork: https://patchwork.freedesktop.org/patch/653583/
    Signed-off-by: Rob Clark <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Zimmermann <[email protected]>
Date:   Mon Apr 7 15:47:24 2025 +0200

    drm/simpledrm: Do not upcast in release helpers
    
    [ Upstream commit d231cde7c84359fb18fb268cf6cff03b5bce48ff ]
    
    The res pointer passed to simpledrm_device_release_clocks() and
    simpledrm_device_release_regulators() points to an instance of
    struct simpledrm_device. No need to upcast from struct drm_device.
    The upcast is harmless, as DRM device is the first field in struct
    simpledrm_device.
    
    Signed-off-by: Thomas Zimmermann <[email protected]>
    Fixes: 11e8f5fd223b ("drm: Add simpledrm driver")
    Cc: <[email protected]> # v5.14+
    Reviewed-by: Javier Martinez Canillas <[email protected]>
    Reviewed-by: Jocelyn Falempe <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Sasha Levin <[email protected]>

Author: Maíra Canal <[email protected]>
Date:   Sat Jun 28 19:42:42 2025 -0300

    drm/v3d: Disable interrupts before resetting the GPU
    
    [ Upstream commit 226862f50a7a88e4e4de9abbf36c64d19acd6fd0 ]
    
    Currently, an interrupt can be triggered during a GPU reset, which can
    lead to GPU hangs and NULL pointer dereference in an interrupt context
    as shown in the following trace:
    
     [  314.035040] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000c0
     [  314.043822] Mem abort info:
     [  314.046606]   ESR = 0x0000000096000005
     [  314.050347]   EC = 0x25: DABT (current EL), IL = 32 bits
     [  314.055651]   SET = 0, FnV = 0
     [  314.058695]   EA = 0, S1PTW = 0
     [  314.061826]   FSC = 0x05: level 1 translation fault
     [  314.066694] Data abort info:
     [  314.069564]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
     [  314.075039]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
     [  314.080080]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
     [  314.085382] user pgtable: 4k pages, 39-bit VAs, pgdp=0000000102728000
     [  314.091814] [00000000000000c0] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000
     [  314.100511] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP
     [  314.106770] Modules linked in: v3d i2c_brcmstb vc4 snd_soc_hdmi_codec gpu_sched drm_shmem_helper drm_display_helper cec drm_dma_helper drm_kms_helper drm drm_panel_orientation_quirks snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd backlight
     [  314.129654] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.25+rpt-rpi-v8 #1  Debian 1:6.12.25-1+rpt1
     [  314.139388] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
     [  314.145211] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
     [  314.152165] pc : v3d_irq+0xec/0x2e0 [v3d]
     [  314.156187] lr : v3d_irq+0xe0/0x2e0 [v3d]
     [  314.160198] sp : ffffffc080003ea0
     [  314.163502] x29: ffffffc080003ea0 x28: ffffffec1f184980 x27: 021202b000000000
     [  314.170633] x26: ffffffec1f17f630 x25: ffffff8101372000 x24: ffffffec1f17d9f0
     [  314.177764] x23: 000000000000002a x22: 000000000000002a x21: ffffff8103252000
     [  314.184895] x20: 0000000000000001 x19: 00000000deadbeef x18: 0000000000000000
     [  314.192026] x17: ffffff94e51d2000 x16: ffffffec1dac3cb0 x15: c306000000000000
     [  314.199156] x14: 0000000000000000 x13: b2fc982e03cc5168 x12: 0000000000000001
     [  314.206286] x11: ffffff8103f8bcc0 x10: ffffffec1f196868 x9 : ffffffec1dac3874
     [  314.213416] x8 : 0000000000000000 x7 : 0000000000042a3a x6 : ffffff810017a180
     [  314.220547] x5 : ffffffec1ebad400 x4 : ffffffec1ebad320 x3 : 00000000000bebeb
     [  314.227677] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
     [  314.234807] Call trace:
     [  314.237243]  v3d_irq+0xec/0x2e0 [v3d]
     [  314.240906]  __handle_irq_event_percpu+0x58/0x218
     [  314.245609]  handle_irq_event+0x54/0xb8
     [  314.249439]  handle_fasteoi_irq+0xac/0x240
     [  314.253527]  handle_irq_desc+0x48/0x68
     [  314.257269]  generic_handle_domain_irq+0x24/0x38
     [  314.261879]  gic_handle_irq+0x48/0xd8
     [  314.265533]  call_on_irq_stack+0x24/0x58
     [  314.269448]  do_interrupt_handler+0x88/0x98
     [  314.273624]  el1_interrupt+0x34/0x68
     [  314.277193]  el1h_64_irq_handler+0x18/0x28
     [  314.281281]  el1h_64_irq+0x64/0x68
     [  314.284673]  default_idle_call+0x3c/0x168
     [  314.288675]  do_idle+0x1fc/0x230
     [  314.291895]  cpu_startup_entry+0x3c/0x50
     [  314.295810]  rest_init+0xe4/0xf0
     [  314.299030]  start_kernel+0x5e8/0x790
     [  314.302684]  __primary_switched+0x80/0x90
     [  314.306691] Code: 940029eb 360ffc13 f9442ea0 52800001 (f9406017)
     [  314.312775] ---[ end trace 0000000000000000 ]---
     [  314.317384] Kernel panic - not syncing: Oops: Fatal exception in interrupt
     [  314.324249] SMP: stopping secondary CPUs
     [  314.328167] Kernel Offset: 0x2b9da00000 from 0xffffffc080000000
     [  314.334076] PHYS_OFFSET: 0x0
     [  314.336946] CPU features: 0x08,00002013,c0200000,0200421b
     [  314.342337] Memory Limit: none
     [  314.345382] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---
    
    Before resetting the GPU, it's necessary to disable all interrupts and
    deal with any interrupt handler still in-flight. Otherwise, the GPU might
    reset with jobs still running, or yet, an interrupt could be handled
    during the reset.
    
    Cc: [email protected]
    Fixes: 57692c94dcbe ("drm/v3d: Introduce a new DRM driver for Broadcom V3D V3.x+")
    Reviewed-by: Juan A. Suarez <[email protected]>
    Reviewed-by: Iago Toral Quiroga <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Maíra Canal <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Alok Tiwari <[email protected]>
Date:   Sat Jun 28 07:56:05 2025 -0700

    enic: fix incorrect MTU comparison in enic_change_mtu()
    
    [ Upstream commit aaf2b2480375099c022a82023e1cd772bf1c6a5d ]
    
    The comparison in enic_change_mtu() incorrectly used the current
    netdev->mtu instead of the new new_mtu value when warning about
    an MTU exceeding the port MTU. This could suppress valid warnings
    or issue incorrect ones.
    
    Fix the condition and log to properly reflect the new_mtu.
    
    Fixes: ab123fe071c9 ("enic: handle mtu change for vf properly")
    Signed-off-by: Alok Tiwari <[email protected]>
    Acked-by: John Daley <[email protected]>
    Reviewed-by: Simon Horman <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Fourier <[email protected]>
Date:   Wed Jun 25 16:16:24 2025 +0200

    ethernet: atl1: Add missing DMA mapping error checks and count errors
    
    [ Upstream commit d72411d20905180cdc452c553be17481b24463d2 ]
    
    The `dma_map_XXX()` functions can fail and must be checked using
    `dma_mapping_error()`.  This patch adds proper error handling for all
    DMA mapping calls.
    
    In `atl1_alloc_rx_buffers()`, if DMA mapping fails, the buffer is
    deallocated and marked accordingly.
    
    In `atl1_tx_map()`, previously mapped buffers are unmapped and the
    packet is dropped on failure.
    
    If `atl1_xmit_frame()` drops the packet, increment the tx_error counter.
    
    Fixes: f3cc28c79760 ("Add Attansic L1 ethernet driver.")
    Signed-off-by: Thomas Fourier <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Chao Yu <[email protected]>
Date:   Sun Dec 10 17:20:40 2023 +0800

    f2fs: add tracepoint for f2fs_vm_page_mkwrite()
    
    [ Upstream commit 87f3afd366f7c668be0269efda8a89741a3ea6b3 ]
    
    This patch adds to support tracepoint for f2fs_vm_page_mkwrite(),
    meanwhile it prints more details for trace_f2fs_filemap_fault().
    
    Signed-off-by: Chao Yu <[email protected]>
    Signed-off-by: Jaegeuk Kim <[email protected]>
    Stable-dep-of: ba8dac350faf ("f2fs: fix to zero post-eof page")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Chao Yu <[email protected]>
Date:   Tue Aug 13 22:13:24 2024 +0800

    f2fs: convert f2fs_vm_page_mkwrite() to use folio
    
    [ Upstream commit aec5755951b74e3bbb5ddee39ac142a788547854 ]
    
    Convert to use folio, so that we can get rid of 'page->index' to
    prepare for removal of 'index' field in structure page [1].
    
    [1] https://lore.kernel.org/all/[email protected]/
    
    Cc: Matthew Wilcox <[email protected]>
    Signed-off-by: Chao Yu <[email protected]>
    Signed-off-by: Jaegeuk Kim <[email protected]>
    Stable-dep-of: ba8dac350faf ("f2fs: fix to zero post-eof page")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Chao Yu <[email protected]>
Date:   Thu Mar 14 10:05:28 2024 +0800

    f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault
    
    commit eb70d5a6c932d9d23f4bb3e7b83782c21ac4b064 upstream.
    
    syzbot reports a f2fs bug as below:
    
    BUG: KASAN: slab-use-after-free in f2fs_filemap_fault+0xd1/0x2c0 fs/f2fs/file.c:49
    Read of size 8 at addr ffff88807bb22680 by task syz-executor184/5058
    
    CPU: 0 PID: 5058 Comm: syz-executor184 Not tainted 6.7.0-syzkaller-09928-g052d534373b7 #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
     print_address_description mm/kasan/report.c:377 [inline]
     print_report+0x163/0x540 mm/kasan/report.c:488
     kasan_report+0x142/0x170 mm/kasan/report.c:601
     f2fs_filemap_fault+0xd1/0x2c0 fs/f2fs/file.c:49
     __do_fault+0x131/0x450 mm/memory.c:4376
     do_shared_fault mm/memory.c:4798 [inline]
     do_fault mm/memory.c:4872 [inline]
     do_pte_missing mm/memory.c:3745 [inline]
     handle_pte_fault mm/memory.c:5144 [inline]
     __handle_mm_fault+0x23b7/0x72b0 mm/memory.c:5285
     handle_mm_fault+0x27e/0x770 mm/memory.c:5450
     do_user_addr_fault arch/x86/mm/fault.c:1364 [inline]
     handle_page_fault arch/x86/mm/fault.c:1507 [inline]
     exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1563
     asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
    
    The root cause is: in f2fs_filemap_fault(), vmf->vma may be not alive after
    filemap_fault(), so it may cause use-after-free issue when accessing
    vmf->vma->vm_flags in trace_f2fs_filemap_fault(). So it needs to keep vm_flags
    in separated temporary variable for tracepoint use.
    
    Fixes: 87f3afd366f7 ("f2fs: add tracepoint for f2fs_vm_page_mkwrite()")
    Reported-and-tested-by: [email protected]
    Closes: https://lore.kernel.org/lkml/[email protected]
    Cc: Ed Tsai <[email protected]>
    Suggested-by: Hillf Danton <[email protected]>
    Signed-off-by: Chao Yu <[email protected]>
    Signed-off-by: Jaegeuk Kim <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Chao Yu <[email protected]>
Date:   Thu Jun 5 11:26:33 2025 +0800

    f2fs: fix to zero post-eof page
    
    [ Upstream commit ba8dac350faf16afc129ce6303ca4feaf083ccb1 ]
    
    fstest reports a f2fs bug:
    
    #generic/363 42s ... [failed, exit status 1]- output mismatch (see /share/git/fstests/results//generic/363.out.bad)
    #    --- tests/generic/363.out   2025-01-12 21:57:40.271440542 +0800
    #    +++ /share/git/fstests/results//generic/363.out.bad 2025-05-19 19:55:58.000000000 +0800
    #    @@ -1,2 +1,78 @@
    #     QA output created by 363
    #     fsx -q -S 0 -e 1 -N 100000
    #    +READ BAD DATA: offset = 0xd6fb, size = 0xf044, fname = /mnt/f2fs/junk
    #    +OFFSET      GOOD    BAD     RANGE
    #    +0x1540d     0x0000  0x2a25  0x0
    #    +operation# (mod 256) for the bad data may be 37
    #    +0x1540e     0x0000  0x2527  0x1
    #    ...
    #    (Run 'diff -u /share/git/fstests/tests/generic/363.out /share/git/fstests/results//generic/363.out.bad'  to see the entire diff)
    Ran: generic/363
    Failures: generic/363
    Failed 1 of 1 tests
    
    The root cause is user can update post-eof page via mmap [1], however, f2fs
    missed to zero post-eof page in below operations, so, once it expands i_size,
    then it will include dummy data locates previous post-eof page, so during
    below operations, we need to zero post-eof page.
    
    Operations which can include dummy data after previous i_size after expanding
    i_size:
    - write
    - mapwrite [1]
    - truncate
    - fallocate
     * preallocate
     * zero_range
     * insert_range
     * collapse_range
    - clone_range (doesn’t support in f2fs)
    - copy_range (doesn’t support in f2fs)
    
    [1] https://man7.org/linux/man-pages/man2/mmap.2.html 'BUG section'
    
    Cc: [email protected]
    Signed-off-by: Chao Yu <[email protected]>
    Reviewed-by: Zhiguo Niu <[email protected]>
    Signed-off-by: Jaegeuk Kim <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Daeho Jeong <[email protected]>
Date:   Thu Apr 11 10:54:10 2024 -0700

    f2fs: prevent writing without fallocate() for pinned files
    
    [ Upstream commit 3fdd89b452c2ea5e2195d6e315bef122769584c9 ]
    
    In a case writing without fallocate(), we can't guarantee it's allocated
    in the conventional area for zoned stroage. To make it consistent across
    storage devices, we disallow it regardless of storage device types.
    
    Signed-off-by: Daeho Jeong <[email protected]>
    Reviewed-by: Chao Yu <[email protected]>
    Signed-off-by: Jaegeuk Kim <[email protected]>
    Stable-dep-of: ba8dac350faf ("f2fs: fix to zero post-eof page")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Shivank Garg <[email protected]>
Date:   Fri Jun 20 07:03:30 2025 +0000

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass
    
    [ Upstream commit cbe4134ea4bc493239786220bd69cb8a13493190 ]
    
    Export anon_inode_make_secure_inode() to allow KVM guest_memfd to create
    anonymous inodes with proper security context. This replaces the current
    pattern of calling alloc_anon_inode() followed by
    inode_init_security_anon() for creating security context manually.
    
    This change also fixes a security regression in secretmem where the
    S_PRIVATE flag was not cleared after alloc_anon_inode(), causing
    LSM/SELinux checks to be bypassed for secretmem file descriptors.
    
    As guest_memfd currently resides in the KVM module, we need to export this
    symbol for use outside the core kernel. In the future, guest_memfd might be
    moved to core-mm, at which point the symbols no longer would have to be
    exported. When/if that happens is still unclear.
    
    Fixes: 2bfe15c52612 ("mm: create security context for memfd_secret inodes")
    Suggested-by: David Hildenbrand <[email protected]>
    Suggested-by: Mike Rapoport <[email protected]>
    Signed-off-by: Shivank Garg <[email protected]>
    Link: https://lore.kernel.org/[email protected]
    Acked-by: "Mike Rapoport (Microsoft)" <[email protected]>
    Signed-off-by: Christian Brauner <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Michael J. Ruhl <[email protected]>
Date:   Fri Jun 27 10:35:11 2025 -0400

    i2c/designware: Fix an initialization issue
    
    commit 3d30048958e0d43425f6d4e76565e6249fa71050 upstream.
    
    The i2c_dw_xfer_init() function requires msgs and msg_write_idx from the
    dev context to be initialized.
    
    amd_i2c_dw_xfer_quirk() inits msgs and msgs_num, but not msg_write_idx.
    
    This could allow an out of bounds access (of msgs).
    
    Initialize msg_write_idx before calling i2c_dw_xfer_init().
    
    Reviewed-by: Andy Shevchenko <[email protected]>
    Fixes: 17631e8ca2d3 ("i2c: designware: Add driver support for AMD NAVI GPU")
    Cc: <[email protected]> # v5.13+
    Signed-off-by: Michael J. Ruhl <[email protected]>
    Signed-off-by: Andi Shyti <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Vitaly Lifshits <[email protected]>
Date:   Wed Jun 11 15:52:54 2025 +0300

    igc: disable L1.2 PCI-E link substate to avoid performance issue
    
    [ Upstream commit 0325143b59c6c6d79987afc57d2456e7a20d13b7 ]
    
    I226 devices advertise support for the PCI-E link L1.2 substate. However,
    due to a hardware limitation, the exit latency from this low-power state
    is longer than the packet buffer can tolerate under high traffic
    conditions. This can lead to packet loss and degraded performance.
    
    To mitigate this, disable the L1.2 substate. The increased power draw
    between L1.1 and L1.2 is insignificant.
    
    Fixes: 43546211738e ("igc: Add new device ID's")
    Link: https://lore.kernel.org/intel-wired-lan/[email protected]
    Signed-off-by: Vitaly Lifshits <[email protected]>
    Reviewed-by: Aleksandr Loktionov <[email protected]>
    Tested-by: Mor Bar-Gabay <[email protected]>
    Signed-off-by: Tony Nguyen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Jeff LaBundy <[email protected]>
Date:   Sun Jun 29 18:33:30 2025 -0700

    Input: iqs7222 - explicitly define number of external channels
    
    commit 63f4970a1219b5256e8ea952096c86dab666d312 upstream.
    
    The number of external channels is assumed to be a multiple of 10,
    but this is not the case for IQS7222D. As a result, some CRx pins
    are wrongly prevented from being assigned to some channels.
    
    Address this problem by explicitly defining the number of external
    channels for cases in which the number of external channels is not
    equal to the total number of available channels.
    
    Fixes: dd24e202ac72 ("Input: iqs7222 - add support for Azoteq IQS7222D")
    Signed-off-by: Jeff LaBundy <[email protected]>
    Link: https://lore.kernel.org/r/aGHVf6HkyFZrzTPy@nixie71
    Cc: [email protected]
    Signed-off-by: Dmitry Torokhov <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Nilton Perim Neto <[email protected]>
Date:   Fri Jun 27 16:29:40 2025 -0700

    Input: xpad - support Acer NGR 200 Controller
    
    commit 22c69d786ef8fb789c61ca75492a272774221324 upstream.
    
    Add the NGR 200 Xbox 360 to the list of recognized controllers.
    
    Signed-off-by: Nilton Perim Neto <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Cc: [email protected]
    Signed-off-by: Dmitry Torokhov <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Simon Xue <[email protected]>
Date:   Mon Jun 23 10:00:18 2025 +0800

    iommu/rockchip: prevent iommus dead loop when two masters share one IOMMU
    
    commit 62e062a29ad5133f67c20b333ba0a952a99161ae upstream.
    
    When two masters share an IOMMU, calling ops->of_xlate during
    the second master's driver init may overwrite iommu->domain set
    by the first. This causes the check if (iommu->domain == domain)
    in rk_iommu_attach_device() to fail, resulting in the same
    iommu->node being added twice to &rk_domain->iommus, which can
    lead to an infinite loop in subsequent &rk_domain->iommus operations.
    
    Cc: <[email protected]>
    Fixes: 25c2325575cc ("iommu/rockchip: Add missing set_platform_dma_ops callback")
    Signed-off-by: Simon Xue <[email protected]>
    Reviewed-by: Robin Murphy <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Joerg Roedel <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Borislav Petkov (AMD) <[email protected]>
Date:   Wed Sep 11 11:00:50 2024 +0200

    KVM: SVM: Advertise TSA CPUID bits to guests
    
    Commit 31272abd5974b38ba312e9cf2ec2f09f9dd7dcba upstream.
    
    Synthesize the TSA CPUID feature bits for guests. Set TSA_{SQ,L1}_NO on
    unaffected machines.
    
    Signed-off-by: Borislav Petkov (AMD) <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Dan Carpenter <[email protected]>
Date:   Mon Jun 30 14:36:40 2025 -0500

    lib: test_objagg: Set error message in check_expect_hints_stats()
    
    [ Upstream commit e6ed134a4ef592fe1fd0cafac9683813b3c8f3e8 ]
    
    Smatch complains that the error message isn't set in the caller:
    
        lib/test_objagg.c:923 test_hints_case2()
        error: uninitialized symbol 'errmsg'.
    
    This static checker warning only showed up after a recent refactoring
    but the bug dates back to when the code was originally added.  This
    likely doesn't affect anything in real life.
    
    Reported-by: kernel test robot <[email protected]>
    Closes: https://lore.kernel.org/r/[email protected]/
    Fixes: 0a020d416d0a ("lib: introduce initial implementation of object aggregation manager")
    Signed-off-by: Dan Carpenter <[email protected]>
    Reviewed-by: Ido Schimmel <[email protected]>
    Reviewed-by: Simon Horman <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Greg Kroah-Hartman <[email protected]>
Date:   Thu Jul 10 16:03:22 2025 +0200

    Linux 6.6.97
    
    Link: https://lore.kernel.org/r/[email protected]
    Tested-by: Shuah Khan <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Tested-by: Florian Fainelli <[email protected]>
    Tested-by: Mark Brown <[email protected]>
    Tested-by: Harshit Mogalapalli <[email protected]>
    Tested-by: Ron Economos <[email protected]>
    Tested-by: Jon Hunter <[email protected]>
    Tested-by: Miguel Ojeda <[email protected]>
    Tested-by: Linux Kernel Functional Testing <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Oliver Neukum <[email protected]>
Date:   Thu Jun 5 14:28:45 2025 +0200

    Logitech C-270 even more broken
    
    commit cee4392a57e14a799fbdee193bc4c0de65b29521 upstream.
    
    Some varieties of this device don't work with
    RESET_RESUME alone.
    
    Signed-off-by: Oliver Neukum <[email protected]>
    Cc: stable <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Avri Altman <[email protected]>
Date:   Mon May 26 14:44:45 2025 +0300

    mmc: core: sd: Apply BROKEN_SD_DISCARD quirk earlier
    
    commit 009c3a4bc41e855fd76f92727f9fbae4e5917d7f upstream.
    
    Move the BROKEN_SD_DISCARD quirk for certain SanDisk SD cards from the
    `mmc_blk_fixups[]` to `mmc_sd_fixups[]`. This ensures the quirk is
    applied earlier in the device initialization process, aligning with the
    reasoning in [1]. Applying the quirk sooner prevents the kernel from
    incorrectly enabling discard support on affected cards during initial
    setup.
    
    [1] https://lore.kernel.org/all/[email protected]
    
    Fixes: 07d2872bf4c8 ("mmc: core: Add SD card quirk for broken discard")
    Signed-off-by: Avri Altman <[email protected]>
    Cc: [email protected]
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Ulf Hansson <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Victor Shih <[email protected]>
Date:   Fri Jun 6 19:01:20 2025 +0800

    mmc: sdhci: Add a helper function for dump register in dynamic debug mode
    
    commit 2881ba9af073faa8ee7408a8d1e0575e50eb3f6c upstream.
    
    Add a helper function for dump register in dynamic debug mode.
    
    Signed-off-by: Victor Shih <[email protected]>
    Acked-by: Adrian Hunter <[email protected]>
    Cc: [email protected]
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Ulf Hansson <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Peter Zijlstra <[email protected]>
Date:   Fri May 2 16:12:09 2025 +0200

    module: Provide EXPORT_SYMBOL_GPL_FOR_MODULES() helper
    
    [ Upstream commit 707f853d7fa3ce323a6875487890c213e34d81a0 ]
    
    Helper macro to more easily limit the export of a symbol to a given
    list of modules.
    
    Eg:
    
      EXPORT_SYMBOL_GPL_FOR_MODULES(preempt_notifier_inc, "kvm");
    
    will limit the use of said function to kvm.ko, any other module trying
    to use this symbol will refure to load (and get modpost build
    failures).
    
    Requested-by: Masahiro Yamada <[email protected]>
    Requested-by: Christoph Hellwig <[email protected]>
    Signed-off-by: Peter Zijlstra <[email protected]>
    Reviewed-by: Petr Pavlu <[email protected]>
    Signed-off-by: Masahiro Yamada <[email protected]>
    Stable-dep-of: cbe4134ea4bc ("fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Pablo Martin-Gomez <[email protected]>
Date:   Wed Jun 18 13:35:16 2025 +0200

    mtd: spinand: fix memory leak of ECC engine conf
    
    [ Upstream commit 6463cbe08b0cbf9bba8763306764f5fd643023e1 ]
    
    Memory allocated for the ECC engine conf is not released during spinand
    cleanup. Below kmemleak trace is seen for this memory leak:
    
    unreferenced object 0xffffff80064f00e0 (size 8):
      comm "swapper/0", pid 1, jiffies 4294937458
      hex dump (first 8 bytes):
        00 00 00 00 00 00 00 00                          ........
      backtrace (crc 0):
        kmemleak_alloc+0x30/0x40
        __kmalloc_cache_noprof+0x208/0x3c0
        spinand_ondie_ecc_init_ctx+0x114/0x200
        nand_ecc_init_ctx+0x70/0xa8
        nanddev_ecc_engine_init+0xec/0x27c
        spinand_probe+0xa2c/0x1620
        spi_mem_probe+0x130/0x21c
        spi_probe+0xf0/0x170
        really_probe+0x17c/0x6e8
        __driver_probe_device+0x17c/0x21c
        driver_probe_device+0x58/0x180
        __device_attach_driver+0x15c/0x1f8
        bus_for_each_drv+0xec/0x150
        __device_attach+0x188/0x24c
        device_initial_probe+0x10/0x20
        bus_probe_device+0x11c/0x160
    
    Fix the leak by calling nanddev_ecc_engine_cleanup() inside
    spinand_cleanup().
    
    Signed-off-by: Pablo Martin-Gomez <[email protected]>
    Signed-off-by: Miquel Raynal <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Masami Hiramatsu (Google) <[email protected]>
Date:   Thu Jun 5 10:07:38 2025 +0900

    mtk-sd: Fix a pagefault in dma_unmap_sg() for not prepared data
    
    commit 539d80575b810c7a5987c7ac8915e3bc99c03695 upstream.
    
    When swiotlb buffer is full, the dma_map_sg() returns 0 to
    msdc_prepare_data(), but it does not check it and sets the
    MSDC_PREPARE_FLAG.
    
    swiotlb_tbl_map_single() /* prints "swiotlb buffer is full" */
      <-swiotlb_map()
        <-dma_direct_map_page()
          <-dma_direct_map_sg()
            <-__dma_map_sg_attrs()
              <-dma_map_sg_attrs()
                <-dma_map_sg()  /* returns 0 (pages mapped) */
                  <-msdc_prepare_data()
    
    Then, the msdc_unprepare_data() checks MSDC_PREPARE_FLAG and calls
    dma_unmap_sg() with unmapped pages. It causes a page fault.
    
    To fix this problem, Do not set MSDC_PREPARE_FLAG if dma_map_sg()
    fails because this is not prepared.
    
    Fixes: 208489032bdd ("mmc: mediatek: Add Mediatek MMC driver")
    Signed-off-by: Masami Hiramatsu (Google) <[email protected]>
    Tested-by: Sergey Senozhatsky <[email protected]>
    Reviewed-by: AngeloGioacchino Del Regno <[email protected]>
    Cc: [email protected]
    Link: https://lore.kernel.org/r/174908565814.4056588.769599127120955383.stgit@mhiramat.tok.corp.google.com
    Signed-off-by: Ulf Hansson <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Masami Hiramatsu (Google) <[email protected]>
Date:   Thu Jun 12 20:26:10 2025 +0900

    mtk-sd: Prevent memory corruption from DMA map failure
    
    commit f5de469990f19569627ea0dd56536ff5a13beaa3 upstream.
    
    If msdc_prepare_data() fails to map the DMA region, the request is
    not prepared for data receiving, but msdc_start_data() proceeds
    the DMA with previous setting.
    Since this will lead a memory corruption, we have to stop the
    request operation soon after the msdc_prepare_data() fails to
    prepare it.
    
    Signed-off-by: Masami Hiramatsu (Google) <[email protected]>
    Fixes: 208489032bdd ("mmc: mediatek: Add Mediatek MMC driver")
    Cc: [email protected]
    Link: https://lore.kernel.org/r/174972756982.3337526.6755001617701603082.stgit@mhiramat.tok.corp.google.com
    Signed-off-by: Ulf Hansson <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Sergey Senozhatsky <[email protected]>
Date:   Wed Jun 25 14:20:37 2025 +0900

    mtk-sd: reset host->mrq on prepare_data() error
    
    commit ec54c0a20709ed6e56f40a8d59eee725c31a916b upstream.
    
    Do not leave host with dangling ->mrq pointer if we hit
    the msdc_prepare_data() error out path.
    
    Signed-off-by: Sergey Senozhatsky <[email protected]>
    Reviewed-by: Masami Hiramatsu (Google) <[email protected]>
    Fixes: f5de469990f1 ("mtk-sd: Prevent memory corruption from DMA map failure")
    Cc: [email protected]
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Ulf Hansson <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Lion Ackermann <[email protected]>
Date:   Mon Jun 30 15:27:30 2025 +0200

    net/sched: Always pass notifications when child class becomes empty
    
    [ Upstream commit 103406b38c600fec1fe375a77b27d87e314aea09 ]
    
    Certain classful qdiscs may invoke their classes' dequeue handler on an
    enqueue operation. This may unexpectedly empty the child qdisc and thus
    make an in-flight class passive via qlen_notify(). Most qdiscs do not
    expect such behaviour at this point in time and may re-activate the
    class eventually anyways which will lead to a use-after-free.
    
    The referenced fix commit attempted to fix this behavior for the HFSC
    case by moving the backlog accounting around, though this turned out to
    be incomplete since the parent's parent may run into the issue too.
    The following reproducer demonstrates this use-after-free:
    
        tc qdisc add dev lo root handle 1: drr
        tc filter add dev lo parent 1: basic classid 1:1
        tc class add dev lo parent 1: classid 1:1 drr
        tc qdisc add dev lo parent 1:1 handle 2: hfsc def 1
        tc class add dev lo parent 2: classid 2:1 hfsc rt m1 8 d 1 m2 0
        tc qdisc add dev lo parent 2:1 handle 3: netem
        tc qdisc add dev lo parent 3:1 handle 4: blackhole
    
        echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888
        tc class delete dev lo classid 1:1
        echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888
    
    Since backlog accounting issues leading to a use-after-frees on stale
    class pointers is a recurring pattern at this point, this patch takes
    a different approach. Instead of trying to fix the accounting, the patch
    ensures that qdisc_tree_reduce_backlog always calls qlen_notify when
    the child qdisc is empty. This solves the problem because deletion of
    qdiscs always involves a call to qdisc_reset() and / or
    qdisc_purge_queue() which ultimately resets its qlen to 0 thus causing
    the following qdisc_tree_reduce_backlog() to report to the parent. Note
    that this may call qlen_notify on passive classes multiple times. This
    is not a problem after the recent patch series that made all the
    classful qdiscs qlen_notify() handlers idempotent.
    
    Fixes: 3f981138109f ("sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()")
    Signed-off-by: Lion Ackermann <[email protected]>
    Reviewed-by: Jamal Hadi Salim <[email protected]>
    Acked-by: Cong Wang <[email protected]>
    Acked-by: Jamal Hadi Salim <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Oleksij Rempel <[email protected]>
Date:   Fri Jun 27 07:13:46 2025 +0200

    net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect
    
    [ Upstream commit 6c7ffc9af7186ed79403a3ffee9a1e5199fc7450 ]
    
    Remove redundant netif_napi_del() call from disconnect path.
    
    A WARN may be triggered in __netif_napi_del_locked() during USB device
    disconnect:
    
      WARNING: CPU: 0 PID: 11 at net/core/dev.c:7417 __netif_napi_del_locked+0x2b4/0x350
    
    This happens because netif_napi_del() is called in the disconnect path while
    NAPI is still enabled. However, it is not necessary to call netif_napi_del()
    explicitly, since unregister_netdev() will handle NAPI teardown automatically
    and safely. Removing the redundant call avoids triggering the warning.
    
    Full trace:
     lan78xx 1-1:1.0 enu1: Failed to read register index 0x000000c4. ret = -ENODEV
     lan78xx 1-1:1.0 enu1: Failed to set MAC down with error -ENODEV
     lan78xx 1-1:1.0 enu1: Link is Down
     lan78xx 1-1:1.0 enu1: Failed to read register index 0x00000120. ret = -ENODEV
     ------------[ cut here ]------------
     WARNING: CPU: 0 PID: 11 at net/core/dev.c:7417 __netif_napi_del_locked+0x2b4/0x350
     Modules linked in: flexcan can_dev fuse
     CPU: 0 UID: 0 PID: 11 Comm: kworker/0:1 Not tainted 6.16.0-rc2-00624-ge926949dab03 #9 PREEMPT
     Hardware name: SKOV IMX8MP CPU revC - bd500 (DT)
     Workqueue: usb_hub_wq hub_event
     pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
     pc : __netif_napi_del_locked+0x2b4/0x350
     lr : __netif_napi_del_locked+0x7c/0x350
     sp : ffffffc085b673c0
     x29: ffffffc085b673c0 x28: ffffff800b7f2000 x27: ffffff800b7f20d8
     x26: ffffff80110bcf58 x25: ffffff80110bd978 x24: 1ffffff0022179eb
     x23: ffffff80110bc000 x22: ffffff800b7f5000 x21: ffffff80110bc000
     x20: ffffff80110bcf38 x19: ffffff80110bcf28 x18: dfffffc000000000
     x17: ffffffc081578940 x16: ffffffc08284cee0 x15: 0000000000000028
     x14: 0000000000000006 x13: 0000000000040000 x12: ffffffb0022179e8
     x11: 1ffffff0022179e7 x10: ffffffb0022179e7 x9 : dfffffc000000000
     x8 : 0000004ffdde8619 x7 : ffffff80110bcf3f x6 : 0000000000000001
     x5 : ffffff80110bcf38 x4 : ffffff80110bcf38 x3 : 0000000000000000
     x2 : 0000000000000000 x1 : 1ffffff0022179e7 x0 : 0000000000000000
     Call trace:
      __netif_napi_del_locked+0x2b4/0x350 (P)
      lan78xx_disconnect+0xf4/0x360
      usb_unbind_interface+0x158/0x718
      device_remove+0x100/0x150
      device_release_driver_internal+0x308/0x478
      device_release_driver+0x1c/0x30
      bus_remove_device+0x1a8/0x368
      device_del+0x2e0/0x7b0
      usb_disable_device+0x244/0x540
      usb_disconnect+0x220/0x758
      hub_event+0x105c/0x35e0
      process_one_work+0x760/0x17b0
      worker_thread+0x768/0xce8
      kthread+0x3bc/0x690
      ret_from_fork+0x10/0x20
     irq event stamp: 211604
     hardirqs last  enabled at (211603): [<ffffffc0828cc9ec>] _raw_spin_unlock_irqrestore+0x84/0x98
     hardirqs last disabled at (211604): [<ffffffc0828a9a84>] el1_dbg+0x24/0x80
     softirqs last  enabled at (211296): [<ffffffc080095f10>] handle_softirqs+0x820/0xbc8
     softirqs last disabled at (210993): [<ffffffc080010288>] __do_softirq+0x18/0x20
     ---[ end trace 0000000000000000 ]---
     lan78xx 1-1:1.0 enu1: failed to kill vid 0081/0
    
    Fixes: ec4c7e12396b ("lan78xx: Introduce NAPI polling support")
    Suggested-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Oleksij Rempel <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kuniyuki Iwashima <[email protected]>
Date:   Thu Jun 12 14:52:50 2025 -0700

    nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails.
    
    [ Upstream commit e8d6f3ab59468e230f3253efe5cb63efa35289f7 ]
    
    syzbot reported a warning below [1] following a fault injection in
    nfs_fs_proc_net_init(). [0]
    
    When nfs_fs_proc_net_init() fails, /proc/net/rpc/nfs is not removed.
    
    Later, rpc_proc_exit() tries to remove /proc/net/rpc, and the warning
    is logged as the directory is not empty.
    
    Let's handle the error of nfs_fs_proc_net_init() properly.
    
    [0]:
    FAULT_INJECTION: forcing a failure.
    name failslab, interval 1, probability 0, space 0, times 0
    CPU: 1 UID: 0 PID: 6120 Comm: syz.2.27 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full)
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
    Call Trace:
     <TASK>
      dump_stack_lvl (lib/dump_stack.c:123)
     should_fail_ex (lib/fault-inject.c:73 lib/fault-inject.c:174)
     should_failslab (mm/failslab.c:46)
     kmem_cache_alloc_noprof (mm/slub.c:4178 mm/slub.c:4204)
     __proc_create (fs/proc/generic.c:427)
     proc_create_reg (fs/proc/generic.c:554)
     proc_create_net_data (fs/proc/proc_net.c:120)
     nfs_fs_proc_net_init (fs/nfs/client.c:1409)
     nfs_net_init (fs/nfs/inode.c:2600)
     ops_init (net/core/net_namespace.c:138)
     setup_net (net/core/net_namespace.c:443)
     copy_net_ns (net/core/net_namespace.c:576)
     create_new_namespaces (kernel/nsproxy.c:110)
     unshare_nsproxy_namespaces (kernel/nsproxy.c:218 (discriminator 4))
     ksys_unshare (kernel/fork.c:3123)
     __x64_sys_unshare (kernel/fork.c:3190)
     do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)
     entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
     </TASK>
    
    [1]:
    remove_proc_entry: removing non-empty directory 'net/rpc', leaking at least 'nfs'
     WARNING: CPU: 1 PID: 6120 at fs/proc/generic.c:727 remove_proc_entry+0x45e/0x530 fs/proc/generic.c:727
    Modules linked in:
    CPU: 1 UID: 0 PID: 6120 Comm: syz.2.27 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full)
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
     RIP: 0010:remove_proc_entry+0x45e/0x530 fs/proc/generic.c:727
    Code: 3c 02 00 0f 85 85 00 00 00 48 8b 93 d8 00 00 00 4d 89 f0 4c 89 e9 48 c7 c6 40 ba a2 8b 48 c7 c7 60 b9 a2 8b e8 33 81 1d ff 90 <0f> 0b 90 90 e9 5f fe ff ff e8 04 69 5e ff 90 48 b8 00 00 00 00 00
    RSP: 0018:ffffc90003637b08 EFLAGS: 00010282
    RAX: 0000000000000000 RBX: ffff88805f534140 RCX: ffffffff817a92c8
    RDX: ffff88807da99e00 RSI: ffffffff817a92d5 RDI: 0000000000000001
    RBP: ffff888033431ac0 R08: 0000000000000001 R09: 0000000000000000
    R10: 0000000000000001 R11: 0000000000000001 R12: ffff888033431a00
    R13: ffff888033431ae4 R14: ffff888033184724 R15: dffffc0000000000
    FS:  0000555580328500(0000) GS:ffff888124a62000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007f71733743e0 CR3: 000000007f618000 CR4: 00000000003526f0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
      sunrpc_exit_net+0x46/0x90 net/sunrpc/sunrpc_syms.c:76
      ops_exit_list net/core/net_namespace.c:200 [inline]
      ops_undo_list+0x2eb/0xab0 net/core/net_namespace.c:253
      setup_net+0x2e1/0x510 net/core/net_namespace.c:457
      copy_net_ns+0x2a6/0x5f0 net/core/net_namespace.c:574
      create_new_namespaces+0x3ea/0xa90 kernel/nsproxy.c:110
      unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:218
      ksys_unshare+0x45b/0xa40 kernel/fork.c:3121
      __do_sys_unshare kernel/fork.c:3192 [inline]
      __se_sys_unshare kernel/fork.c:3190 [inline]
      __x64_sys_unshare+0x31/0x40 kernel/fork.c:3190
      do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
      do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
     entry_SYSCALL_64_after_hwframe+0x77/0x7f
    RIP: 0033:0x7fa1a6b8e929
    Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
    RSP: 002b:00007fff3a090368 EFLAGS: 00000246 ORIG_RAX: 0000000000000110
    RAX: ffffffffffffffda RBX: 00007fa1a6db5fa0 RCX: 00007fa1a6b8e929
    RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000040000080
    RBP: 00007fa1a6c10b39 R08: 0000000000000000 R09: 0000000000000000
    R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
    R13: 00007fa1a6db5fa0 R14: 00007fa1a6db5fa0 R15: 0000000000000001
     </TASK>
    
    Fixes: d47151b79e32 ("nfs: expose /proc/net/sunrpc/nfs in net namespaces")
    Reported-by: [email protected]
    Closes: https://syzkaller.appspot.com/bug?extid=a4cc4ac22daa4a71b87c
    Tested-by: [email protected]
    Signed-off-by: Kuniyuki Iwashima <[email protected]>
    Signed-off-by: Anna Schumaker <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Trond Myklebust <[email protected]>
Date:   Thu Jun 19 15:16:11 2025 -0400

    NFSv4/flexfiles: Fix handling of NFS level errors in I/O
    
    [ Upstream commit 38074de35b015df5623f524d6f2b49a0cd395c40 ]
    
    Allow the flexfiles error handling to recognise NFS level errors (as
    opposed to RPC level errors) and handle them separately. The main
    motivator is the NFSERR_PERM errors that get returned if the NFS client
    connects to the data server through a port number that is lower than
    1024. In that case, the client should disconnect and retry a READ on a
    different data server, or it should retry a WRITE after reconnecting.
    
    Reviewed-by: Tigran Mkrtchyan <[email protected]>
    Fixes: d67ae825a59d ("pnfs/flexfiles: Add the FlexFile Layout Driver")
    Signed-off-by: Trond Myklebust <[email protected]>
    Signed-off-by: Anna Schumaker <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Benjamin Coddington <[email protected]>
Date:   Thu Jun 19 11:02:21 2025 -0400

    NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN
    
    [ Upstream commit c01776287414ca43412d1319d2877cbad65444ac ]
    
    We found a few different systems hung up in writeback waiting on the same
    page lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in
    pnfs_update_layout(), however the pnfs_layout_hdr's plh_outstanding count
    was zero.
    
    It seems most likely that this is another race between the waiter and waker
    similar to commit ed0172af5d6f ("SUNRPC: Fix a race to wake a sync task").
    Fix it up by applying the advised barrier.
    
    Fixes: 880265c77ac4 ("pNFS: Avoid a live lock condition in pnfs_update_layout()")
    Signed-off-by: Benjamin Coddington <[email protected]>
    Signed-off-by: Anna Schumaker <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Fourier <[email protected]>
Date:   Mon Jun 30 10:36:43 2025 +0200

    nui: Fix dma_mapping_error() check
    
    [ Upstream commit 561aa0e22b70a5e7246b73d62a824b3aef3fc375 ]
    
    dma_map_XXX() functions return values DMA_MAPPING_ERROR as error values
    which is often ~0.  The error value should be tested with
    dma_mapping_error().
    
    This patch creates a new function in niu_ops to test if the mapping
    failed.  The test is fixed in niu_rbr_add_page(), added in
    niu_start_xmit() and the successfully mapped pages are unmaped upon error.
    
    Fixes: ec2deec1f352 ("niu: Fix to check for dma mapping errors.")
    Signed-off-by: Thomas Fourier <[email protected]>
    Reviewed-by: Simon Horman <[email protected]>
    Signed-off-by: David S. Miller <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: David Thompson <[email protected]>
Date:   Fri Jun 13 21:46:08 2025 +0000

    platform/mellanox: mlxbf-tmfifo: fix vring_desc.len assignment
    
    [ Upstream commit 109f4d29dade8ae5b4ac6325af9d1bc24b4230f8 ]
    
    Fix warnings reported by sparse, related to incorrect type:
    drivers/platform/mellanox/mlxbf-tmfifo.c:284:38: warning: incorrect type in assignment (different base types)
    drivers/platform/mellanox/mlxbf-tmfifo.c:284:38:    expected restricted __virtio32 [usertype] len
    drivers/platform/mellanox/mlxbf-tmfifo.c:284:38:    got unsigned long
    
    Reported-by: kernel test robot <[email protected]>
    Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
    Fixes: 78034cbece79 ("platform/mellanox: mlxbf-tmfifo: Drop the Rx packet if no more descriptors")
    Signed-off-by: David Thompson <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Alok Tiwari <[email protected]>
Date:   Mon Jun 30 03:58:08 2025 -0700

    platform/mellanox: mlxreg-lc: Fix logic error in power state check
    
    [ Upstream commit 644bec18e705ca41d444053407419a21832fcb2f ]
    
    Fixes a logic issue in mlxreg_lc_completion_notify() where the
    intention was to check if MLXREG_LC_POWERED flag is not set before
    powering on the device.
    
    The original code used "state & ~MLXREG_LC_POWERED" to check for the
    absence of the POWERED bit. However this condition evaluates to true
    even when other bits are set, leading to potentially incorrect
    behavior.
    
    Corrected the logic to explicitly check for the absence of
    MLXREG_LC_POWERED using !(state & MLXREG_LC_POWERED).
    
    Fixes: 62f9529b8d5c ("platform/mellanox: mlxreg-lc: Add initial support for Nvidia line card devices")
    Suggested-by: Vadim Pasternak <[email protected]>
    Signed-off-by: Alok Tiwari <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Alok Tiwari <[email protected]>
Date:   Sun Jun 22 00:29:12 2025 -0700

    platform/mellanox: nvsw-sn2201: Fix bus number in adapter error message
    
    [ Upstream commit d07143b507c51c04c091081627c5a130e9d3c517 ]
    
    change error log to use correct bus number from main_mux_devs
    instead of cpld_devs.
    
    Fixes: 662f24826f95 ("platform/mellanox: Add support for new SN2201 system")
    Signed-off-by: Alok Tiwari <[email protected]>
    Reviewed-by: Vadim Pasternak <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Mario Limonciello <[email protected]>
Date:   Wed Jun 11 15:33:40 2025 -0500

    platform/x86/amd/pmc: Add PCSpecialist Lafite Pro V 14M to 8042 quirks list
    
    [ Upstream commit 9ba75ccad85708c5a484637dccc1fc59295b0a83 ]
    
    Every other s2idle cycle fails to reach hardware sleep when keyboard
    wakeup is enabled.  This appears to be an EC bug, but the vendor
    refuses to fix it.
    
    It was confirmed that turning off i8042 wakeup avoids ths issue
    (albeit keyboard wakeup is disabled).  Take the lesser of two evils
    and add it to the i8042 quirk list.
    
    Reported-by: Raoul <[email protected]>
    Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220116
    Tested-by: Raoul <[email protected]>
    Signed-off-by: Mario Limonciello <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Weißschuh <[email protected]>
Date:   Sat Jan 4 00:05:13 2025 +0100

    platform/x86: dell-sysman: Directly use firmware_attributes_class
    
    [ Upstream commit 501d2f0e78951b9a933bbff73404b25aec45f389 ]
    
    The usage of the lifecycle functions is not necessary anymore.
    
    Signed-off-by: Thomas Weißschuh <[email protected]>
    Reviewed-by: Armin Wolf <[email protected]>
    Reviewed-by: Mario Limonciello <[email protected]>
    Reviewed-by: Mark Pearson <[email protected]>
    Tested-by: Mark Pearson <[email protected]>
    Link: https://lore.kernel.org/r/20250104-firmware-attributes-simplify-v1-5-949f9709e405@weissschuh.net
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Stable-dep-of: 314e5ad4782d ("platform/x86: dell-wmi-sysman: Fix class device unregistration")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kurt Borja <[email protected]>
Date:   Wed Jun 25 22:17:37 2025 -0300

    platform/x86: dell-wmi-sysman: Fix class device unregistration
    
    [ Upstream commit 314e5ad4782d08858b3abc325c0487bd2abc23a1 ]
    
    Devices under the firmware_attributes_class do not have unique a dev_t.
    Therefore, device_unregister() should be used instead of
    device_destroy(), since the latter may match any device with a given
    dev_t.
    
    Fixes: e8a60aa7404b ("platform/x86: Introduce support for Systems Management Driver over WMI for Dell Systems")
    Signed-off-by: Kurt Borja <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kurt Borja <[email protected]>
Date:   Mon Jun 30 00:43:12 2025 -0300

    platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks
    
    [ Upstream commit eb617dd25ca176f3fee24f873f0fd60010773d67 ]
    
    After retrieving WMI data blocks in sysfs callbacks, check for the
    validity of them before dereferencing their content.
    
    Reported-by: Jan Graczyk <[email protected]>
    Closes: https://lore.kernel.org/r/CAHk-=wgMiSKXf7SvQrfEnxVtmT=QVQPjJdNjfm3aXS7wc=rzTw@mail.gmail.com/
    Fixes: e8a60aa7404b ("platform/x86: Introduce support for Systems Management Driver over WMI for Dell Systems")
    Suggested-by: Linus Torvalds <[email protected]>
    Reviewed-by: Armin Wolf <[email protected]>
    Signed-off-by: Kurt Borja <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Weißschuh <[email protected]>
Date:   Sat Jan 4 00:05:09 2025 +0100

    platform/x86: firmware_attributes_class: Move include linux/device/class.h
    
    [ Upstream commit d0eee1be379204d2ee6cdb09bd98b3fd0165b6d3 ]
    
    The header firmware_attributes_class.h uses 'struct class'. It should
    also include the necessary dependency header.
    
    Signed-off-by: Thomas Weißschuh <[email protected]>
    Reviewed-by: Armin Wolf <[email protected]>
    Reviewed-by: Mario Limonciello <[email protected]>
    Reviewed-by: Mark Pearson <[email protected]>
    Tested-by: Mark Pearson <[email protected]>
    Link: https://lore.kernel.org/r/20250104-firmware-attributes-simplify-v1-1-949f9709e405@weissschuh.net
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Stable-dep-of: 5ff1fbb30597 ("platform/x86: think-lmi: Fix class device unregistration")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Weißschuh <[email protected]>
Date:   Sat Jan 4 00:05:10 2025 +0100

    platform/x86: firmware_attributes_class: Simplify API
    
    [ Upstream commit d03cfde56f5cf9ec50b4cf099a42bf056fc80ddd ]
    
    The module core already guarantees that a module can only be unloaded
    after all other modules using its symbols have been unloaded.
    As it's already the responsibility of the drivers using
    firmware_attributes_class to clean up their devices before unloading,
    the lifetime of the firmware_attributes_class can be bound to the
    lifetime of the module.
    This enables the direct usage of firmware_attributes_class from the
    drivers, without having to go through the lifecycle functions,
    leading to simplifications for both the subsystem and its users.
    
    Signed-off-by: Thomas Weißschuh <[email protected]>
    Reviewed-by: Armin Wolf <[email protected]>
    Reviewed-by: Mario Limonciello <[email protected]>
    Reviewed-by: Mark Pearson <[email protected]>
    Tested-by: Mark Pearson <[email protected]>
    Link: https://lore.kernel.org/r/20250104-firmware-attributes-simplify-v1-2-949f9709e405@weissschuh.net
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Stable-dep-of: 5ff1fbb30597 ("platform/x86: think-lmi: Fix class device unregistration")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Weißschuh <[email protected]>
Date:   Sat Jan 4 00:05:12 2025 +0100

    platform/x86: hp-bioscfg: Directly use firmware_attributes_class
    
    [ Upstream commit 63f8c058036057644f095123a35895cd11639b88 ]
    
    The usage of the lifecycle functions is not necessary anymore.
    
    Signed-off-by: Thomas Weißschuh <[email protected]>
    Reviewed-by: Armin Wolf <[email protected]>
    Reviewed-by: Mario Limonciello <[email protected]>
    Reviewed-by: Mark Pearson <[email protected]>
    Tested-by: Mark Pearson <[email protected]>
    Link: https://lore.kernel.org/r/20250104-firmware-attributes-simplify-v1-4-949f9709e405@weissschuh.net
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Stable-dep-of: 11cba4793b95 ("platform/x86: hp-bioscfg: Fix class device unregistration")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kurt Borja <[email protected]>
Date:   Wed Jun 25 22:17:35 2025 -0300

    platform/x86: hp-bioscfg: Fix class device unregistration
    
    [ Upstream commit 11cba4793b95df3bc192149a6eb044f69aa0b99e ]
    
    Devices under the firmware_attributes_class do not have unique a dev_t.
    Therefore, device_unregister() should be used instead of
    device_destroy(), since the latter may match any device with a given
    dev_t.
    
    Fixes: a34fc329b189 ("platform/x86: hp-bioscfg: bioscfg")
    Signed-off-by: Kurt Borja <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Ricardo B. Marliere <[email protected]>
Date:   Tue Mar 5 15:55:04 2024 -0300

    platform/x86: make fw_attr_class constant
    
    [ Upstream commit 5878e5b760b6fcf7bc00dec085ba2b439a929871 ]
    
    Since commit 43a7206b0963 ("driver core: class: make class_register() take
    a const *"), the driver core allows for struct class to be in read-only
    memory, so move the fw_attr_class structure to be declared at build time
    placing it into read-only memory, instead of having to be dynamically
    allocated at boot time.
    
    Cc: Greg Kroah-Hartman <[email protected]>
    Suggested-by: Greg Kroah-Hartman <[email protected]>
    Signed-off-by: "Ricardo B. Marliere" <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Stable-dep-of: 5ff1fbb30597 ("platform/x86: think-lmi: Fix class device unregistration")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kurt Borja <[email protected]>
Date:   Mon Jun 30 14:31:19 2025 -0300

    platform/x86: think-lmi: Create ksets consecutively
    
    commit 8dab34ca77293b409c3223636dde915a22656748 upstream.
    
    Avoid entering tlmi_release_attr() in error paths if both ksets are not
    yet created.
    
    This is accomplished by initializing them side by side.
    
    Reviewed-by: Mark Pearson <[email protected]>
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Cc: [email protected]
    Signed-off-by: Kurt Borja <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Thomas Weißschuh <[email protected]>
Date:   Sat Jan 4 00:05:11 2025 +0100

    platform/x86: think-lmi: Directly use firmware_attributes_class
    
    [ Upstream commit 55922403807a12d4f96c67ba01a920edfb6f2633 ]
    
    The usage of the lifecycle functions is not necessary anymore.
    
    Signed-off-by: Thomas Weißschuh <[email protected]>
    Reviewed-by: Armin Wolf <[email protected]>
    Reviewed-by: Mario Limonciello <[email protected]>
    Reviewed-by: Mark Pearson <[email protected]>
    Tested-by: Mark Pearson <[email protected]>
    Link: https://lore.kernel.org/r/20250104-firmware-attributes-simplify-v1-3-949f9709e405@weissschuh.net
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Stable-dep-of: 5ff1fbb30597 ("platform/x86: think-lmi: Fix class device unregistration")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kurt Borja <[email protected]>
Date:   Wed Jun 25 22:17:36 2025 -0300

    platform/x86: think-lmi: Fix class device unregistration
    
    [ Upstream commit 5ff1fbb3059730700b4823f43999fc1315984632 ]
    
    Devices under the firmware_attributes_class do not have unique a dev_t.
    Therefore, device_unregister() should be used instead of
    device_destroy(), since the latter may match any device with a given
    dev_t.
    
    Fixes: a40cd7ef22fb ("platform/x86: think-lmi: Add WMI interface support on Lenovo platforms")
    Signed-off-by: Kurt Borja <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Kurt Borja <[email protected]>
Date:   Mon Jun 30 14:31:20 2025 -0300

    platform/x86: think-lmi: Fix kobject cleanup
    
    commit 9110056fe10b0519529bdbbac37311a5037ea0c2 upstream.
    
    In tlmi_analyze(), allocated structs with an embedded kobject are freed
    in error paths after the they were already initialized.
    
    Fix this by first by avoiding the initialization of kobjects in
    tlmi_analyze() and then by correctly cleaning them up in
    tlmi_release_attr() using their kset's kobject list.
    
    Fixes: a40cd7ef22fb ("platform/x86: think-lmi: Add WMI interface support on Lenovo platforms")
    Fixes: 30e78435d3bf ("platform/x86: think-lmi: Split kobject_init() and kobject_add() calls")
    Cc: [email protected]
    Reviewed-by: Mark Pearson <[email protected]>
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Kurt Borja <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Kurt Borja <[email protected]>
Date:   Mon Jun 30 14:31:21 2025 -0300

    platform/x86: think-lmi: Fix sysfs group cleanup
    
    commit 4f30f946f27b7f044cf8f3f1f353dee1dcd3517a upstream.
    
    Many error paths in tlmi_sysfs_init() lead to sysfs groups being removed
    when they were not even created.
    
    Fix this by letting the kobject core manage these groups through their
    kobj_type's defult_groups.
    
    Fixes: a40cd7ef22fb ("platform/x86: think-lmi: Add WMI interface support on Lenovo platforms")
    Cc: [email protected]
    Reviewed-by: Mark Pearson <[email protected]>
    Reviewed-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Kurt Borja <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Ilpo Järvinen <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Zhang Rui <[email protected]>
Date:   Thu Jun 19 15:13:40 2025 +0800

    powercap: intel_rapl: Do not change CLAMPING bit if ENABLE bit cannot be changed
    
    commit 964209202ebe1569c858337441e87ef0f9d71416 upstream.
    
    PL1 cannot be disabled on some platforms. The ENABLE bit is still set
    after software clears it. This behavior leads to a scenario where, upon
    user request to disable the Power Limit through the powercap sysfs, the
    ENABLE bit remains set while the CLAMPING bit is inadvertently cleared.
    
    According to the Intel Software Developer's Manual, the CLAMPING bit,
    "When set, allows the processor to go below the OS requested P states in
    order to maintain the power below specified Platform Power Limit value."
    
    Thus this means the system may operate at higher power levels than
    intended on such platforms.
    
    Enhance the code to check ENABLE bit after writing to it, and stop
    further processing if ENABLE bit cannot be changed.
    
    Reported-by: Srinivas Pandruvada <[email protected]>
    Fixes: 2d281d8196e3 ("PowerCap: Introduce Intel RAPL power capping driver")
    Cc: All applicable <[email protected]>
    Signed-off-by: Zhang Rui <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    [ rjw: Use str_enabled_disabled() instead of open-coded equivalent ]
    Signed-off-by: Rafael J. Wysocki <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Madhavan Srinivasan <[email protected]>
Date:   Sun May 11 09:41:11 2025 +0530

    powerpc/kernel: Fix ppc_save_regs inclusion in build
    
    commit 93bd4a80efeb521314485a06d8c21157240497bb upstream.
    
    Recent patch fixed an old commit
    'fc2a5a6161a2 ("powerpc/64s: ppc_save_regs is now needed for all 64s builds")'
    which is to include building of ppc_save_reg.c only when XMON
    and KEXEC_CORE and PPC_BOOK3S are enabled. This was valid, since
    ppc_save_regs was called only in replay_system_reset() of old
    irq.c which was under BOOK3S.
    
    But there has been multiple refactoring of irq.c and have
    added call to ppc_save_regs() from __replay_soft_interrupts
    -> replay_soft_interrupts which is part of irq_64.c included
    under CONFIG_PPC64. And since ppc_save_regs is called in
    CRASH_DUMP path as part of crash_setup_regs in kexec.h,
    CONFIG_PPC32 also needs it.
    
    So with this recent patch which enabled the building of
    ppc_save_regs.c caused a build break when none of these
    (XMON, KEXEC_CORE, BOOK3S) where enabled as part of config.
    Patch to enable building of ppc_save_regs.c by defaults.
    
    Signed-off-by: Madhavan Srinivasan <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Cc: Guenter Roeck <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Madhavan Srinivasan <[email protected]>
Date:   Sat May 17 19:52:37 2025 +0530

    powerpc: Fix struct termio related ioctl macros
    
    [ Upstream commit ab107276607af90b13a5994997e19b7b9731e251 ]
    
    Since termio interface is now obsolete, include/uapi/asm/ioctls.h
    has some constant macros referring to "struct termio", this caused
    build failure at userspace.
    
    In file included from /usr/include/asm/ioctl.h:12,
                     from /usr/include/asm/ioctls.h:5,
                     from tst-ioctls.c:3:
    tst-ioctls.c: In function 'get_TCGETA':
    tst-ioctls.c:12:10: error: invalid application of 'sizeof' to incomplete type 'struct termio'
       12 |   return TCGETA;
          |          ^~~~~~
    
    Even though termios.h provides "struct termio", trying to juggle definitions around to
    make it compile could introduce regressions. So better to open code it.
    
    Reported-by: Tulio Magno <[email protected]>
    Suggested-by: Nicholas Piggin <[email protected]>
    Tested-by: Justin M. Forbes <[email protected]>
    Reviewed-by: Michael Ellerman <[email protected]>
    Closes: https://lore.kernel.org/linuxppc-dev/[email protected]/
    Signed-off-by: Madhavan Srinivasan <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Sasha Levin <[email protected]>

Author: Uladzislau Rezki (Sony) <[email protected]>
Date:   Tue Jun 10 19:34:48 2025 +0200

    rcu: Return early if callback is not specified
    
    [ Upstream commit 33b6a1f155d627f5bd80c7485c598ce45428f74f ]
    
    Currently the call_rcu() API does not check whether a callback
    pointer is NULL. If NULL is passed, rcu_core() will try to invoke
    it, resulting in NULL pointer dereference and a kernel crash.
    
    To prevent this and improve debuggability, this patch adds a check
    for NULL and emits a kernel stack trace to help identify a faulty
    caller.
    
    Signed-off-by: Uladzislau Rezki (Sony) <[email protected]>
    Reviewed-by: Joel Fernandes <[email protected]>
    Signed-off-by: Joel Fernandes <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Patrisious Haddad <[email protected]>
Date:   Mon Jun 16 12:14:53 2025 +0300

    RDMA/mlx5: Fix CC counters query for MPV
    
    [ Upstream commit acd245b1e33fc4b9d0f2e3372021d632f7ee0652 ]
    
    In case, CC counters are querying for the second port use the correct
    core device for the query instead of always using the master core device.
    
    Fixes: aac4492ef23a ("IB/mlx5: Update counter implementation for dual port RoCE")
    Signed-off-by: Patrisious Haddad <[email protected]>
    Reviewed-by: Michael Guralnik <[email protected]>
    Link: https://patch.msgid.link/9cace74dcf106116118bebfa9146d40d4166c6b0.1750064969.git.leon@kernel.org
    Signed-off-by: Leon Romanovsky <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Patrisious Haddad <[email protected]>
Date:   Mon Jun 16 12:14:52 2025 +0300

    RDMA/mlx5: Fix HW counters query for non-representor devices
    
    [ Upstream commit 3cc1dbfddf88dc5ecce0a75185061403b1f7352d ]
    
    To get the device HW counters, a non-representor switchdev device
    should use the mlx5_ib_query_q_counters() function and query all of
    the available counters. While a representor device in switchdev mode
    should use the mlx5_ib_query_q_counters_vport() function and query only
    the Q_Counters without the PPCNT counters and congestion control counters,
    since they aren't relevant for a representor device.
    
    Currently a non-representor switchdev device skips querying the PPCNT
    counters and congestion control counters, leaving them unupdated.
    Fix that by properly querying those counters for non-representor devices.
    
    Fixes: d22467a71ebe ("RDMA/mlx5: Expand switchdev Q-counters to expose representor statistics")
    Signed-off-by: Patrisious Haddad <[email protected]>
    Reviewed-by: Maher Sanalla <[email protected]>
    Link: https://patch.msgid.link/56bf8af4ca8c58e3fb9f7e47b1dca2009eeeed81.1750064969.git.leon@kernel.org
    Signed-off-by: Leon Romanovsky <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Patrisious Haddad <[email protected]>
Date:   Mon Jun 16 12:14:54 2025 +0300

    RDMA/mlx5: Fix vport loopback for MPV device
    
    [ Upstream commit a9a9e68954f29b1e197663f76289db4879fd51bb ]
    
    Always enable vport loopback for both MPV devices on driver start.
    
    Previously in some cases related to MPV RoCE, packets weren't correctly
    executing loopback check at vport in FW, since it was disabled.
    Due to complexity of identifying such cases for MPV always enable vport
    loopback for both GVMIs when binding the slave to the master port.
    
    Fixes: 0042f9e458a5 ("RDMA/mlx5: Enable vport loopback when user context or QP mandate")
    Signed-off-by: Patrisious Haddad <[email protected]>
    Reviewed-by: Mark Bloch <[email protected]>
    Link: https://patch.msgid.link/d4298f5ebb2197459e9e7221c51ecd6a34699847.1750064969.git.leon@kernel.org
    Signed-off-by: Leon Romanovsky <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Mark Zhang <[email protected]>
Date:   Tue Jun 17 11:13:55 2025 +0300

    RDMA/mlx5: Initialize obj_event->obj_sub_list before xa_insert
    
    [ Upstream commit 8edab8a72d67742f87e9dc2e2b0cdfddda5dc29a ]
    
    The obj_event may be loaded immediately after inserted, then if the
    list_head is not initialized then we may get a poisonous pointer.  This
    fixes the crash below:
    
     mlx5_core 0000:03:00.0: MLX5E: StrdRq(1) RqSz(8) StrdSz(2048) RxCqeCmprss(0 enhanced)
     mlx5_core.sf mlx5_core.sf.4: firmware version: 32.38.3056
     mlx5_core 0000:03:00.0 en3f0pf0sf2002: renamed from eth0
     mlx5_core.sf mlx5_core.sf.4: Rate limit: 127 rates are supported, range: 0Mbps to 195312Mbps
     IPv6: ADDRCONF(NETDEV_CHANGE): en3f0pf0sf2002: link becomes ready
     Unable to handle kernel NULL pointer dereference at virtual address 0000000000000060
     Mem abort info:
       ESR = 0x96000006
       EC = 0x25: DABT (current EL), IL = 32 bits
       SET = 0, FnV = 0
       EA = 0, S1PTW = 0
     Data abort info:
       ISV = 0, ISS = 0x00000006
       CM = 0, WnR = 0
     user pgtable: 4k pages, 48-bit VAs, pgdp=00000007760fb000
     [0000000000000060] pgd=000000076f6d7003, p4d=000000076f6d7003, pud=0000000777841003, pmd=0000000000000000
     Internal error: Oops: 96000006 [#1] SMP
     Modules linked in: ipmb_host(OE) act_mirred(E) cls_flower(E) sch_ingress(E) mptcp_diag(E) udp_diag(E) raw_diag(E) unix_diag(E) tcp_diag(E) inet_diag(E) binfmt_misc(E) bonding(OE) rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) isofs(E) cdrom(E) mst_pciconf(OE) ib_umad(OE) mlx5_ib(OE) ipmb_dev_int(OE) mlx5_core(OE) kpatch_15237886(OEK) mlxdevm(OE) auxiliary(OE) ib_uverbs(OE) ib_core(OE) psample(E) mlxfw(OE) tls(E) sunrpc(E) vfat(E) fat(E) crct10dif_ce(E) ghash_ce(E) sha1_ce(E) sbsa_gwdt(E) virtio_console(E) ext4(E) mbcache(E) jbd2(E) xfs(E) libcrc32c(E) mmc_block(E) virtio_net(E) net_failover(E) failover(E) sha2_ce(E) sha256_arm64(E) nvme(OE) nvme_core(OE) gpio_mlxbf3(OE) mlx_compat(OE) mlxbf_pmc(OE) i2c_mlxbf(OE) sdhci_of_dwcmshc(OE) pinctrl_mlxbf3(OE) mlxbf_pka(OE) gpio_generic(E) i2c_core(E) mmc_core(E) mlxbf_gige(OE) vitesse(E) pwr_mlxbf(OE) mlxbf_tmfifo(OE) micrel(E) mlxbf_bootctl(OE) virtio_ring(E) virtio(E) ipmi_devintf(E) ipmi_msghandler(E)
      [last unloaded: mst_pci]
     CPU: 11 PID: 20913 Comm: rte-worker-11 Kdump: loaded Tainted: G           OE K   5.10.134-13.1.an8.aarch64 #1
     Hardware name: https://www.mellanox.com BlueField-3 SmartNIC Main Card/BlueField-3 SmartNIC Main Card, BIOS 4.2.2.12968 Oct 26 2023
     pstate: a0400089 (NzCv daIf +PAN -UAO -TCO BTYPE=--)
     pc : dispatch_event_fd+0x68/0x300 [mlx5_ib]
     lr : devx_event_notifier+0xcc/0x228 [mlx5_ib]
     sp : ffff80001005bcf0
     x29: ffff80001005bcf0 x28: 0000000000000001
     x27: ffff244e0740a1d8 x26: ffff244e0740a1d0
     x25: ffffda56beff5ae0 x24: ffffda56bf911618
     x23: ffff244e0596a480 x22: ffff244e0596a480
     x21: ffff244d8312ad90 x20: ffff244e0596a480
     x19: fffffffffffffff0 x18: 0000000000000000
     x17: 0000000000000000 x16: ffffda56be66d620
     x15: 0000000000000000 x14: 0000000000000000
     x13: 0000000000000000 x12: 0000000000000000
     x11: 0000000000000040 x10: ffffda56bfcafb50
     x9 : ffffda5655c25f2c x8 : 0000000000000010
     x7 : 0000000000000000 x6 : ffff24545a2e24b8
     x5 : 0000000000000003 x4 : ffff80001005bd28
     x3 : 0000000000000000 x2 : 0000000000000000
     x1 : ffff244e0596a480 x0 : ffff244d8312ad90
     Call trace:
      dispatch_event_fd+0x68/0x300 [mlx5_ib]
      devx_event_notifier+0xcc/0x228 [mlx5_ib]
      atomic_notifier_call_chain+0x58/0x80
      mlx5_eq_async_int+0x148/0x2b0 [mlx5_core]
      atomic_notifier_call_chain+0x58/0x80
      irq_int_handler+0x20/0x30 [mlx5_core]
      __handle_irq_event_percpu+0x60/0x220
      handle_irq_event_percpu+0x3c/0x90
      handle_irq_event+0x58/0x158
      handle_fasteoi_irq+0xfc/0x188
      generic_handle_irq+0x34/0x48
      ...
    
    Fixes: 759738537142 ("IB/mlx5: Enable subscription for device events over DEVX")
    Link: https://patch.msgid.link/r/3ce7f20e0d1a03dc7de6e57494ec4b8eaf1f05c2.1750147949.git.leon@kernel.org
    Signed-off-by: Mark Zhang <[email protected]>
    Signed-off-by: Leon Romanovsky <[email protected]>
    Signed-off-by: Jason Gunthorpe <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Heiko Stuebner <[email protected]>
Date:   Fri Jun 6 21:04:18 2025 +0200

    regulator: fan53555: add enable_time support and soft-start times
    
    [ Upstream commit 8acfb165a492251a08a22a4fa6497a131e8c2609 ]
    
    The datasheets for all the fan53555 variants (and clones using the same
    interface) define so called soft start times, from enabling the regulator
    until at least some percentage of the output (i.e. 92% for the rk860x
    types) are available.
    
    The regulator framework supports this with the enable_time property
    but currently the fan53555 driver does not define enable_times for any
    variant.
    
    I ran into a problem with this while testing the new driver for the
    Rockchip NPUs (rocket), which does runtime-pm including disabling and
    enabling a rk8602 as needed. When reenabling the regulator while running
    a load, fatal hangs could be observed while enabling the associated
    power-domain, which the regulator supplies.
    
    Experimentally setting the regulator to always-on, made the issue
    disappear, leading to the missing delay to let power stabilize.
    And as expected, setting the enable-time to a non-zero value
    according to the datasheet also resolved the regulator-issue.
    
    The datasheets in nearly all cases only specify "typical" values,
    except for the fan53555 type 08. There both a typical and maximum
    value are listed - 40uS apart.
    
    For all typical values I've added 100uS to be on the safe side.
    Individual details for the relevant regulators below:
    
    - fan53526:
      The datasheet for all variants lists a typical value of 150uS, so
      make that 250uS with safety margin.
    - fan53555:
      types 08 and 18 (unsupported) are given a typical enable time of 135uS
      but also a maximum of 175uS so use that value. All the other types only
      have a typical time in the datasheet of 300uS, so give a bit margin by
      setting it to 400uS.
    - rk8600 + rk8602:
      Datasheet reports a typical value of 260us, so use 360uS to be safe.
    - syr82x + syr83x:
      All datasheets report typical soft-start values of 300uS for these
      regulators, so use 400uS.
    - tcs452x:
      Datasheet sadly does not report a soft-start time, so I've not set
      an enable-time
    
    Signed-off-by: Heiko Stuebner <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Mark Brown <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Manivannan Sadhasivam <[email protected]>
Date:   Thu Jul 3 16:05:49 2025 +0530

    regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods
    
    commit c9764fd88bc744592b0604ccb6b6fc1a5f76b4e3 upstream.
    
    drvdata::gpiods is supposed to hold an array of 'gpio_desc' pointers. But
    the memory is allocated for only one pointer. This will lead to
    out-of-bounds access later in the code if 'config::ngpios' is > 1. So
    fix the code to allocate enough memory to hold 'config::ngpios' of GPIO
    descriptors.
    
    While at it, also move the check for memory allocation failure to be below
    the allocation to make it more readable.
    
    Cc: [email protected] # 5.0
    Fixes: d6cd33ad7102 ("regulator: gpio: Convert to use descriptors")
    Signed-off-by: Manivannan Sadhasivam <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Mark Brown <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Joonas Lahtinen <[email protected]>
Date:   Thu May 22 09:41:27 2025 +0300

    Revert "drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1"
    
    [ Upstream commit ed5915cfce2abb9a553c3737badebd4a11d6c9c7 ]
    
    This reverts commit d6e020819612a4a06207af858e0978be4d3e3140.
    
    The IS_DGFX check was put in place because error capture of buffer
    objects is expected to be broken on devices with VRAM.
    
    Userspace fix[1] to the impacted media driver has been submitted, merged
    and a new driver release is out as 25.2.3 where the capture flag is
    dropped on DG1 thus unblocking the usage of media driver on DG1.
    
    [1] https://github.com/intel/media-driver/commit/93c07d9b4b96a78bab21f6acd4eb863f4313ea4a
    
    Cc: [email protected] # v6.0+
    Cc: Ville Syrjälä <[email protected]>
    Cc: Andi Shyti <[email protected]>
    Cc: Matthew Auld <[email protected]>
    Cc: Thomas Hellström <[email protected]>
    Cc: Tvrtko Ursulin <[email protected]>
    Acked-by: Tvrtko Ursulin <[email protected]>
    Reviewed-by: Andi Shyti <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    [Joonas: Update message to point out the merged userspace fix]
    Signed-off-by: Joonas Lahtinen <[email protected]>
    (cherry picked from commit d2dc30e0aa252830f908c8e793d3139d51321370)
    Signed-off-by: Joonas Lahtinen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Ulf Hansson <[email protected]>
Date:   Tue Jun 24 13:09:32 2025 +0200

    Revert "mmc: sdhci: Disable SD card clock before changing parameters"
    
    commit dcc3bcfc5b50c625b475dcc25d167b6b947a6637 upstream.
    
    It has turned out the trying to strictly conform to the SDHCI specification
    is causing problems. Let's revert and start over.
    
    This reverts commit fb3bbc46c94f261b6156ee863c1b06c84cf157dc.
    
    Cc: Erick Shepherd <[email protected]>
    Cc: [email protected]
    Fixes: fb3bbc46c94f ("mmc: sdhci: Disable SD card clock before changing parameters")
    Suggested-by: Adrian Hunter <[email protected]>
    Reported-by: Jonathan Liu <[email protected]>
    Reported-by: Salvatore Bonaccorso <[email protected]>
    Closes: https://bugs.debian.org/1108065
    Acked-by: Adrian Hunter <[email protected]>
    Signed-off-by: Ulf Hansson <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Kohei Enju <[email protected]>
Date:   Sun Jun 29 12:06:31 2025 +0900

    rose: fix dangling neighbour pointers in rose_rt_device_down()
    
    [ Upstream commit 34a500caf48c47d5171f4aa1f237da39b07c6157 ]
    
    There are two bugs in rose_rt_device_down() that can cause
    use-after-free:
    
    1. The loop bound `t->count` is modified within the loop, which can
       cause the loop to terminate early and miss some entries.
    
    2. When removing an entry from the neighbour array, the subsequent entries
       are moved up to fill the gap, but the loop index `i` is still
       incremented, causing the next entry to be skipped.
    
    For example, if a node has three neighbours (A, A, B) with count=3 and A
    is being removed, the second A is not checked.
    
        i=0: (A, A, B) -> (A, B) with count=2
              ^ checked
        i=1: (A, B)    -> (A, B) with count=2
                 ^ checked (B, not A!)
        i=2: (doesn't occur because i < count is false)
    
    This leaves the second A in the array with count=2, but the rose_neigh
    structure has been freed. Code that accesses these entries assumes that
    the first `count` entries are valid pointers, causing a use-after-free
    when it accesses the dangling pointer.
    
    Fix both issues by iterating over the array in reverse order with a fixed
    loop bound. This ensures that all entries are examined and that the removal
    of an entry doesn't affect subsequent iterations.
    
    Reported-by: [email protected]
    Closes: https://syzkaller.appspot.com/bug?extid=e04e2c007ba2c80476cb
    Tested-by: [email protected]
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Kohei Enju <[email protected]>
    Reviewed-by: Simon Horman <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Jakub Kicinski <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Mateusz Jończyk <[email protected]>
Date:   Sat Jun 7 23:06:08 2025 +0200

    rtc: cmos: use spin_lock_irqsave in cmos_interrupt
    
    commit 00a39d8652ff9088de07a6fe6e9e1893452fe0dd upstream.
    
    cmos_interrupt() can be called in a non-interrupt context, such as in
    an ACPI event handler (which runs in an interrupt thread). Therefore,
    usage of spin_lock(&rtc_lock) is insecure. Use spin_lock_irqsave() /
    spin_unlock_irqrestore() instead.
    
    Before a misguided
    commit 6950d046eb6e ("rtc: cmos: Replace spin_lock_irqsave with spin_lock in hard IRQ")
    the cmos_interrupt() function used spin_lock_irqsave(). That commit
    changed it to spin_lock() and broke locking, which was partially fixed in
    commit 13be2efc390a ("rtc: cmos: Disable irq around direct invocation of cmos_interrupt()")
    
    That second commit did not take account of the ACPI fixed event handler
    pathway, however. It introduced local_irq_disable() workarounds in
    cmos_check_wkalrm(), which can cause problems on PREEMPT_RT kernels
    and are now unnecessary.
    
    Add an explicit comment so that this change will not be reverted by
    mistake.
    
    Cc: [email protected]
    Fixes: 6950d046eb6e ("rtc: cmos: Replace spin_lock_irqsave with spin_lock in hard IRQ")
    Signed-off-by: Mateusz Jończyk <[email protected]>
    Reviewed-by: Sebastian Andrzej Siewior <[email protected]>
    Tested-by: Chris Bainbridge <[email protected]>
    Reported-by: Chris Bainbridge <[email protected]>
    Closes: https://lore.kernel.org/all/[email protected]/
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Alexandre Belloni <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Hugo Villeneuve <[email protected]>
Date:   Thu May 29 16:29:22 2025 -0400

    rtc: pcf2127: add missing semicolon after statement
    
    commit 08d82d0cad51c2b1d454fe41ea1ff96ade676961 upstream.
    
    Replace comma with semicolon at the end of the statement when setting
    config.max_register.
    
    Fixes: fd28ceb4603f ("rtc: pcf2127: add variant-specific configuration structure")
    Cc: [email protected]
    Cc: Elena Popa <[email protected]>
    Signed-off-by: Hugo Villeneuve <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Alexandre Belloni <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Elena Popa <[email protected]>
Date:   Fri May 30 13:40:00 2025 +0300

    rtc: pcf2127: fix SPI command byte for PCF2131
    
    commit fa78e9b606a472495ef5b6b3d8b45c37f7727f9d upstream.
    
    PCF2131 was not responding to read/write operations using SPI. PCF2131
    has a different command byte definition, compared to PCF2127/29. Added
    the new command byte definition when PCF2131 is detected.
    
    Fixes: afc505bf9039 ("rtc: pcf2127: add support for PCF2131 RTC")
    Cc: [email protected]
    Signed-off-by: Elena Popa <[email protected]>
    Acked-by: Hugo Villeneuve <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Alexandre Belloni <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Niklas Schnelle <[email protected]>
Date:   Wed Jun 25 11:28:29 2025 +0200

    s390/pci: Do not try re-enabling load/store if device is disabled
    
    commit b97a7972b1f4f81417840b9a2ab0c19722b577d5 upstream.
    
    If a device is disabled unblocking load/store on its own is not useful
    as a full re-enable of the function is necessary anyway. Note that SCLP
    Write Event Data Action Qualifier 0 (Reset) leaves the device disabled
    and triggers this case unless the driver already requests a reset.
    
    Cc: [email protected]
    Fixes: 4cdf2f4e24ff ("s390/pci: implement minimal PCI error recovery")
    Reviewed-by: Farhan Ali <[email protected]>
    Signed-off-by: Niklas Schnelle <[email protected]>
    Signed-off-by: Alexander Gordeev <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Thomas Fourier <[email protected]>
Date:   Tue Jun 17 18:11:11 2025 +0200

    scsi: qla2xxx: Fix DMA mapping test in qla24xx_get_port_database()
    
    [ Upstream commit c3b214719a87735d4f67333a8ef3c0e31a34837c ]
    
    dma_map_XXX() functions return as error values DMA_MAPPING_ERROR which is
    often ~0.  The error value should be tested with dma_mapping_error() like
    it was done in qla26xx_dport_diagnostics().
    
    Fixes: 818c7f87a177 ("scsi: qla2xxx: Add changes in preparation for vendor extended FDMI/RDP")
    Signed-off-by: Thomas Fourier <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Martin K. Petersen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Thomas Fourier <[email protected]>
Date:   Wed Jun 18 09:17:37 2025 +0200

    scsi: qla4xxx: Fix missing DMA mapping error in qla4xxx_alloc_pdu()
    
    [ Upstream commit 00f452a1b084efbe8dcb60a29860527944a002a1 ]
    
    dma_map_XXX() can fail and should be tested for errors with
    dma_mapping_error().
    
    Fixes: b3a271a94d00 ("[SCSI] qla4xxx: support iscsiadm session mgmt")
    Signed-off-by: Thomas Fourier <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Martin K. Petersen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Maurizio Lombardi <[email protected]>
Date:   Thu Jun 12 12:15:56 2025 +0200

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()
    
    [ Upstream commit d8ab68bdb294b09a761e967dad374f2965e1913f ]
    
    The function core_scsi3_decode_spec_i_port(), in its error code path,
    unconditionally calls core_scsi3_lunacl_undepend_item() passing the
    dest_se_deve pointer, which may be NULL.
    
    This can lead to a NULL pointer dereference if dest_se_deve remains
    unset.
    
    SPC-3 PR SPEC_I_PT: Unable to locate dest_tpg
    Unable to handle kernel paging request at virtual address dfff800000000012
    Call trace:
      core_scsi3_lunacl_undepend_item+0x2c/0xf0 [target_core_mod] (P)
      core_scsi3_decode_spec_i_port+0x120c/0x1c30 [target_core_mod]
      core_scsi3_emulate_pro_register+0x6b8/0xcd8 [target_core_mod]
      target_scsi3_emulate_pr_out+0x56c/0x840 [target_core_mod]
    
    Fix this by adding a NULL check before calling
    core_scsi3_lunacl_undepend_item()
    
    Signed-off-by: Maurizio Lombardi <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Mike Christie <[email protected]>
    Reviewed-by: John Meneghini <[email protected]>
    Signed-off-by: Martin K. Petersen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Manivannan Sadhasivam <[email protected]>
Date:   Thu Oct 12 22:51:26 2023 +0530

    scsi: ufs: core: Add OPP support for scaling clocks and regulators
    
    [ Upstream commit 930bd77ebe3dc23b18aa49e55e6a515d5663d67a ]
    
    UFS core is only scaling the clocks during devfreq scaling and
    initialization. But for an optimum power saving, regulators should also be
    scaled along with the clocks.
    
    So let's use the OPP framework which supports scaling clocks, regulators,
    and performance state using OPP table defined in devicetree. For
    accomodating the OPP support, the existing APIs (ufshcd_scale_clks,
    ufshcd_is_devfreq_scaling_required and ufshcd_devfreq_scale) are modified
    to accept "freq" as an argument which in turn used by the OPP helpers.
    
    The OPP support is added along with the old freq-table based clock scaling
    so that the existing platforms work as expected.
    
    Co-developed-by: Krzysztof Kozlowski <[email protected]>
    Signed-off-by: Krzysztof Kozlowski <[email protected]>
    Signed-off-by: Manivannan Sadhasivam <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Martin K. Petersen <[email protected]>
    Stable-dep-of: 2e083cd80229 ("scsi: ufs: core: Fix clk scaling to be conditional in reset and restore")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Peter Wang <[email protected]>
Date:   Thu Aug 31 21:08:25 2023 +0800

    scsi: ufs: core: Fix abnormal scale up after last cmd finish
    
    [ Upstream commit 6fd53da45bbc834b9cfdf707d2f7ebe666667943 ]
    
    When ufshcd_clk_scaling_suspend_work (thread A) running and new command
    coming, ufshcd_clk_scaling_start_busy (thread B) may get host_lock after
    thread A first time release host_lock. Then thread A second time get
    host_lock will set clk_scaling.window_start_t = 0 which scale up clock
    abnormal next polling_ms time.  Also inlines another
    __ufshcd_suspend_clkscaling calls.
    
    Below is racing step:
    1       hba->clk_scaling.suspend_work (Thread A)
            ufshcd_clk_scaling_suspend_work
    2               spin_lock_irqsave(hba->host->host_lock, irq_flags);
    3               hba->clk_scaling.is_suspended = true;
    4               spin_unlock_irqrestore(hba->host->host_lock, irq_flags);
                    __ufshcd_suspend_clkscaling
    7                       spin_lock_irqsave(hba->host->host_lock, flags);
    8                       hba->clk_scaling.window_start_t = 0;
    9                       spin_unlock_irqrestore(hba->host->host_lock, flags);
    
            ufshcd_send_command (Thread B)
                    ufshcd_clk_scaling_start_busy
    5                       spin_lock_irqsave(hba->host->host_lock, flags);
                            ....
    6                       spin_unlock_irqrestore(hba->host->host_lock, flags);
    
    Signed-off-by: Peter Wang <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Bart Van Assche <[email protected]>
    Signed-off-by: Martin K. Petersen <[email protected]>
    Stable-dep-of: 2e083cd80229 ("scsi: ufs: core: Fix clk scaling to be conditional in reset and restore")
    Signed-off-by: Sasha Levin <[email protected]>

Author: anvithdosapati <[email protected]>
Date:   Mon Jun 16 08:57:34 2025 +0000

    scsi: ufs: core: Fix clk scaling to be conditional in reset and restore
    
    [ Upstream commit 2e083cd802294693a5414e4557a183dd7e442e71 ]
    
    In ufshcd_host_reset_and_restore(), scale up clocks only when clock
    scaling is supported. Without this change CPU latency is voted for 0
    (ufshcd_pm_qos_update) during resume unconditionally.
    
    Signed-off-by: anvithdosapati <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Fixes: a3cd5ec55f6c ("scsi: ufs: add load based scaling of UFS gear")
    Cc: [email protected]
    Reviewed-by: Bart Van Assche <[email protected]>
    Signed-off-by: Martin K. Petersen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Bart Van Assche <[email protected]>
Date:   Tue Jun 24 11:16:44 2025 -0700

    scsi: ufs: core: Fix spelling of a sysfs attribute name
    
    [ Upstream commit 021f243627ead17eb6500170256d3d9be787dad8 ]
    
    Change "resourse" into "resource" in the name of a sysfs attribute.
    
    Fixes: d829fc8a1058 ("scsi: ufs: sysfs: unit descriptor")
    Signed-off-by: Bart Van Assche <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Reviewed-by: Avri Altman <[email protected]>
    Signed-off-by: Martin K. Petersen <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Wang Zhaolong <[email protected]>
Date:   Thu Jul 3 21:29:52 2025 +0800

    smb: client: fix race condition in negotiate timeout by using more precise timing
    
    [ Upstream commit 266b5d02e14f3a0e07414e11f239397de0577a1d ]
    
    When the SMB server reboots and the client immediately accesses the mount
    point, a race condition can occur that causes operations to fail with
    "Host is down" error.
    
    Reproduction steps:
      # Mount SMB share
      mount -t cifs //192.168.245.109/TEST /mnt/ -o xxxx
      ls /mnt
    
      # Reboot server
      ssh [email protected] reboot
      ssh [email protected] /path/to/cifs_server_setup.sh
      ssh [email protected] systemctl stop firewalld
    
      # Immediate access fails
      ls /mnt
      ls: cannot access '/mnt': Host is down
    
      # But works if there is a delay
    
    The issue is caused by a race condition between negotiate and reconnect.
    The 20-second negotiate timeout mechanism can interfere with the normal
    recovery process when both are triggered simultaneously.
    
      ls                              cifsd
    ---------------------------------------------------
     cifs_getattr
     cifs_revalidate_dentry
     cifs_get_inode_info
     cifs_get_fattr
     smb2_query_path_info
     smb2_compound_op
     SMB2_open_init
     smb2_reconnect
     cifs_negotiate_protocol
      smb2_negotiate
       cifs_send_recv
        smb_send_rqst
        wait_for_response
                                cifs_demultiplex_thread
                                  cifs_read_from_socket
                                  cifs_readv_from_socket
                                    server_unresponsive
                                    cifs_reconnect
                                      __cifs_reconnect
                                      cifs_abort_connection
                                        mid->mid_state = MID_RETRY_NEEDED
                                        cifs_wake_up_task
        cifs_sync_mid_result
         // case MID_RETRY_NEEDED
         rc = -EAGAIN;
       // In smb2_negotiate()
       rc = -EHOSTDOWN;
    
    The server_unresponsive() timeout triggers cifs_reconnect(), which aborts
    ongoing mid requests and causes the ls command to receive -EAGAIN, leading
    to -EHOSTDOWN.
    
    Fix this by introducing a dedicated `neg_start` field to
    precisely tracks when the negotiate process begins. The timeout check
    now uses this accurate timestamp instead of `lstrp`, ensuring that:
    
    1. Timeout is only triggered after negotiate has actually run for 20s
    2. The mechanism doesn't interfere with concurrent recovery processes
    3. Uninitialized timestamps (value 0) don't trigger false timeouts
    
    Fixes: 7ccc1465465d ("smb: client: fix hang in wait_for_response() for negproto")
    Signed-off-by: Wang Zhaolong <[email protected]>
    Signed-off-by: Steve French <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Philipp Kerling <[email protected]>
Date:   Sun Jun 29 19:05:05 2025 +0200

    smb: client: fix readdir returning wrong type with POSIX extensions
    
    commit b8f89cb723b9e66f5dbd7199e4036fee34fb0de0 upstream.
    
    When SMB 3.1.1 POSIX Extensions are negotiated, userspace applications
    using readdir() or getdents() calls without stat() on each individual file
    (such as a simple "ls" or "find") would misidentify file types and exhibit
    strange behavior such as not descending into directories. The reason for
    this behavior is an oversight in the cifs_posix_to_fattr conversion
    function. Instead of extracting the entry type for cf_dtype from the
    properly converted cf_mode field, it tries to extract the type from the
    PDU. While the wire representation of the entry mode is similar in
    structure to POSIX stat(), the assignments of the entry types are
    different. Applying the S_DT macro to cf_mode instead yields the correct
    result. This is also what the equivalent function
    smb311_posix_info_to_fattr in inode.c already does for stat() etc.; which
    is why "ls -l" would give the correct file type but "ls" would not (as
    identified by the colors).
    
    Cc: [email protected]
    Signed-off-by: Philipp Kerling <[email protected]>
    Signed-off-by: Steve French <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Paulo Alcantara <[email protected]>
Date:   Wed Jun 25 00:00:17 2025 -0300

    smb: client: fix warning when reconnecting channel
    
    [ Upstream commit 3bbe46716092d8ef6b0df4b956f585c5cd0fc78e ]
    
    When reconnecting a channel in smb2_reconnect_server(), a dummy tcon
    is passed down to smb2_reconnect() with ->query_interface
    uninitialized, so we can't call queue_delayed_work() on it.
    
    Fix the following warning by ensuring that we're queueing the delayed
    worker from correct tcon.
    
    WARNING: CPU: 4 PID: 1126 at kernel/workqueue.c:2498 __queue_delayed_work+0x1d2/0x200
    Modules linked in: cifs cifs_arc4 nls_ucs2_utils cifs_md4 [last unloaded: cifs]
    CPU: 4 UID: 0 PID: 1126 Comm: kworker/4:0 Not tainted 6.16.0-rc3 #5 PREEMPT(voluntary)
    Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-4.fc42 04/01/2014
    Workqueue: cifsiod smb2_reconnect_server [cifs]
    RIP: 0010:__queue_delayed_work+0x1d2/0x200
    Code: 41 5e 41 5f e9 7f ee ff ff 90 0f 0b 90 e9 5d ff ff ff bf 02 00
    00 00 e8 6c f3 07 00 89 c3 eb bd 90 0f 0b 90 e9 57 f> 0b 90 e9 65 fe
    ff ff 90 0f 0b 90 e9 72 fe ff ff 90 0f 0b 90 e9
    RSP: 0018:ffffc900014afad8 EFLAGS: 00010003
    RAX: 0000000000000000 RBX: ffff888124d99988 RCX: ffffffff81399cc1
    RDX: dffffc0000000000 RSI: ffff888114326e00 RDI: ffff888124d999f0
    RBP: 000000000000ea60 R08: 0000000000000001 R09: ffffed10249b3331
    R10: ffff888124d9998f R11: 0000000000000004 R12: 0000000000000040
    R13: ffff888114326e00 R14: ffff888124d999d8 R15: ffff888114939020
    FS:  0000000000000000(0000) GS:ffff88829f7fe000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007ffe7a2b4038 CR3: 0000000120a6f000 CR4: 0000000000750ef0
    PKRU: 55555554
    Call Trace:
     <TASK>
     queue_delayed_work_on+0xb4/0xc0
     smb2_reconnect+0xb22/0xf50 [cifs]
     smb2_reconnect_server+0x413/0xd40 [cifs]
     ? __pfx_smb2_reconnect_server+0x10/0x10 [cifs]
     ? local_clock_noinstr+0xd/0xd0
     ? local_clock+0x15/0x30
     ? lock_release+0x29b/0x390
     process_one_work+0x4c5/0xa10
     ? __pfx_process_one_work+0x10/0x10
     ? __list_add_valid_or_report+0x37/0x120
     worker_thread+0x2f1/0x5a0
     ? __kthread_parkme+0xde/0x100
     ? __pfx_worker_thread+0x10/0x10
     kthread+0x1fe/0x380
     ? kthread+0x10f/0x380
     ? __pfx_kthread+0x10/0x10
     ? local_clock_noinstr+0xd/0xd0
     ? ret_from_fork+0x1b/0x1f0
     ? local_clock+0x15/0x30
     ? lock_release+0x29b/0x390
     ? rcu_is_watching+0x20/0x50
     ? __pfx_kthread+0x10/0x10
     ret_from_fork+0x15b/0x1f0
     ? __pfx_kthread+0x10/0x10
     ret_from_fork_asm+0x1a/0x30
     </TASK>
    irq event stamp: 1116206
    hardirqs last  enabled at (1116205): [<ffffffff8143af42>] __up_console_sem+0x52/0x60
    hardirqs last disabled at (1116206): [<ffffffff81399f0e>] queue_delayed_work_on+0x6e/0xc0
    softirqs last  enabled at (1116138): [<ffffffffc04562fd>] __smb_send_rqst+0x42d/0x950 [cifs]
    softirqs last disabled at (1116136): [<ffffffff823d35e1>] release_sock+0x21/0xf0
    
    Cc: [email protected]
    Reported-by: David Howells <[email protected]>
    Fixes: 42ca547b13a2 ("cifs: do not disable interface polling on failure")
    Reviewed-by: David Howells <[email protected]>
    Tested-by: David Howells <[email protected]>
    Reviewed-by: Shyam Prasad N <[email protected]>
    Signed-off-by: Paulo Alcantara (Red Hat) <[email protected]>
    Signed-off-by: David Howells <[email protected]>
    Tested-by: Steve French <[email protected]>
    Signed-off-by: Steve French <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Stefan Metzmacher <[email protected]>
Date:   Sun Jul 6 05:03:16 2025 -0400

    smb: client: remove \t from TP_printk statements
    
    [ Upstream commit e97f9540ce001503a4539f337da742c1dfa7d86a ]
    
    The generate '[FAILED TO PARSE]' strings in trace-cmd report output like this:
    
      rm-5298  [001]  6084.533748493: smb3_exit_err:        [FAILED TO PARSE] xid=972 func_name=cifs_rmdir rc=-39
      rm-5298  [001]  6084.533959234: smb3_enter:           [FAILED TO PARSE] xid=973 func_name=cifs_closedir
      rm-5298  [001]  6084.533967630: smb3_close_enter:     [FAILED TO PARSE] xid=973 fid=94489281833 tid=1 sesid=96758029877361
      rm-5298  [001]  6084.534004008: smb3_cmd_enter:       [FAILED TO PARSE] tid=1 sesid=96758029877361 cmd=6 mid=566
      rm-5298  [001]  6084.552248232: smb3_cmd_done:        [FAILED TO PARSE] tid=1 sesid=96758029877361 cmd=6 mid=566
      rm-5298  [001]  6084.552280542: smb3_close_done:      [FAILED TO PARSE] xid=973 fid=94489281833 tid=1 sesid=96758029877361
      rm-5298  [001]  6084.552316034: smb3_exit_done:       [FAILED TO PARSE] xid=973 func_name=cifs_closedir
    
    Cc: [email protected]
    Signed-off-by: Stefan Metzmacher <[email protected]>
    Signed-off-by: Steve French <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: James Clark <[email protected]>
Date:   Fri Jun 27 11:21:37 2025 +0100

    spi: spi-fsl-dspi: Clear completion counter before initiating transfer
    
    [ Upstream commit fa60c094c19b97e103d653f528f8d9c178b6a5f5 ]
    
    In target mode, extra interrupts can be received between the end of a
    transfer and halting the module if the host continues sending more data.
    If the interrupt from this occurs after the reinit_completion() then the
    completion counter is left at a non-zero value. The next unrelated
    transfer initiated by userspace will then complete immediately without
    waiting for the interrupt or writing to the RX buffer.
    
    Fix it by resetting the counter before the transfer so that lingering
    values are cleared. This is done after clearing the FIFOs and the
    status register but before the transfer is initiated, so no interrupts
    should be received at this point resulting in other race conditions.
    
    Fixes: 4f5ee75ea171 ("spi: spi-fsl-dspi: Replace interruptible wait queue with a simple completion")
    Signed-off-by: James Clark <[email protected]>
    Reviewed-by: Frank Li <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Mark Brown <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Peter Chen <[email protected]>
Date:   Thu Jun 19 09:34:13 2025 +0800

    usb: cdnsp: do not disable slot for disabled slot
    
    commit 7e2c421ef88e9da9c39e01496b7f5b0b354b42bc upstream.
    
    It doesn't need to do it, and the related command event returns
    'Slot Not Enabled Error' status.
    
    Fixes: 3d82904559f4 ("usb: cdnsp: cdns3 Add main part of Cadence USBSSP DRD Driver")
    Cc: stable <[email protected]>
    Suggested-by: Hongliang Yang <[email protected]>
    Reviewed-by: Fugang Duan <[email protected]>
    Signed-off-by: Peter Chen <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Xu Yang <[email protected]>
Date:   Sat Jun 14 20:49:14 2025 +0800

    usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume
    
    commit 31a6afbe86e8e9deba9ab53876ec49eafc7fd901 upstream.
    
    Shawn and John reported a hang issue during system suspend as below:
    
     - USB gadget is enabled as Ethernet
     - There is data transfer over USB Ethernet (scp a big file between host
                                                 and device)
     - Device is going in/out suspend (echo mem > /sys/power/state)
    
    The root cause is the USB device controller is suspended but the USB bus
    is still active which caused the USB host continues to transfer data with
    device and the device continues to queue USB requests (in this case, a
    delayed TCP ACK packet trigger the issue) after controller is suspended,
    however the USB controller clock is already gated off. Then if udc driver
    access registers after that point, the system will hang.
    
    The correct way to avoid such issue is to disconnect device from host when
    the USB bus is not at suspend state. Then the host will receive disconnect
    event and stop data transfer in time. To continue make USB gadget device
    work after system resume, this will reconnect device automatically.
    
    To make usb wakeup work if USB bus is already at suspend state, this will
    keep connection for it only when USB device controller has enabled wakeup
    capability.
    
    Reported-by: Shawn Guo <[email protected]>
    Reported-by: John Ernberg <[email protected]>
    Closes: https://lore.kernel.org/linux-usb/aEZxmlHmjeWcXiF3@dragon/
    Tested-by: John Ernberg <[email protected]> # iMX8QXP
    Fixes: 235ffc17d014 ("usb: chipidea: udc: add suspend/resume support for device controller")
    Cc: stable <[email protected]>
    Reviewed-by: Jun Li <[email protected]>
    Signed-off-by: Xu Yang <[email protected]>
    Acked-by: Peter Chen <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: RD Babiera <[email protected]>
Date:   Wed Jun 18 22:49:42 2025 +0000

    usb: typec: altmodes/displayport: do not index invalid pin_assignments
    
    commit af4db5a35a4ef7a68046883bfd12468007db38f1 upstream.
    
    A poorly implemented DisplayPort Alt Mode port partner can indicate
    that its pin assignment capabilities are greater than the maximum
    value, DP_PIN_ASSIGN_F. In this case, calls to pin_assignment_show
    will cause a BRK exception due to an out of bounds array access.
    
    Prevent for loop in pin_assignment_show from accessing
    invalid values in pin_assignments by adding DP_PIN_ASSIGN_MAX
    value in typec_dp.h and using i < DP_PIN_ASSIGN_MAX as a loop
    condition.
    
    Fixes: 0e3bb7d6894d ("usb: typec: Add driver for DisplayPort alternate mode")
    Cc: stable <[email protected]>
    Signed-off-by: RD Babiera <[email protected]>
    Reviewed-by: Badhri Jagan Sridharan <[email protected]>
    Reviewed-by: Heikki Krogerus <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Andrei Kuchynski <[email protected]>
Date:   Tue Jun 24 13:32:46 2025 +0000

    usb: typec: displayport: Fix potential deadlock
    
    commit 099cf1fbb8afc3771f408109f62bdec66f85160e upstream.
    
    The deadlock can occur due to a recursive lock acquisition of
    `cros_typec_altmode_data::mutex`.
    The call chain is as follows:
    1. cros_typec_altmode_work() acquires the mutex
    2. typec_altmode_vdm() -> dp_altmode_vdm() ->
    3. typec_altmode_exit() -> cros_typec_altmode_exit()
    4. cros_typec_altmode_exit() attempts to acquire the mutex again
    
    To prevent this, defer the `typec_altmode_exit()` call by scheduling
    it rather than calling it directly from within the mutex-protected
    context.
    
    Cc: stable <[email protected]>
    Fixes: b4b38ffb38c9 ("usb: typec: displayport: Receive DP Status Update NAK request exit dp altmode")
    Signed-off-by: Andrei Kuchynski <[email protected]>
    Reviewed-by: Heikki Krogerus <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Raju Rangoju <[email protected]>
Date:   Fri Jun 27 17:41:19 2025 +0300

    usb: xhci: quirk for data loss in ISOC transfers
    
    commit cbc889ab0122366f6cdbe3c28d477c683ebcebc2 upstream.
    
    During the High-Speed Isochronous Audio transfers, xHCI
    controller on certain AMD platforms experiences momentary data
    loss. This results in Missed Service Errors (MSE) being
    generated by the xHCI.
    
    The root cause of the MSE is attributed to the ISOC OUT endpoint
    being omitted from scheduling. This can happen when an IN
    endpoint with a 64ms service interval either is pre-scheduled
    prior to the ISOC OUT endpoint or the interval of the ISOC OUT
    endpoint is shorter than that of the IN endpoint. Consequently,
    the OUT service is neglected when an IN endpoint with a service
    interval exceeding 32ms is scheduled concurrently (every 64ms in
    this scenario).
    
    This issue is particularly seen on certain older AMD platforms.
    To mitigate this problem, it is recommended to adjust the service
    interval of the IN endpoint to not exceed 32ms (interval 8). This
    adjustment ensures that the OUT endpoint will not be bypassed,
    even if a smaller interval value is utilized.
    
    Cc: stable <[email protected]>
    Signed-off-by: Raju Rangoju <[email protected]>
    Signed-off-by: Mathias Nyman <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Bui Quang Minh <[email protected]>
Date:   Mon Jun 30 21:42:10 2025 +0700

    virtio-net: ensure the received length does not exceed allocated size
    
    commit 315dbdd7cdf6aa533829774caaf4d25f1fd20e73 upstream.
    
    In xdp_linearize_page, when reading the following buffers from the ring,
    we forget to check the received length with the true allocate size. This
    can lead to an out-of-bound read. This commit adds that missing check.
    
    Cc: <[email protected]>
    Fixes: 4941d472bf95 ("virtio-net: do not reset during XDP set")
    Signed-off-by: Bui Quang Minh <[email protected]>
    Acked-by: Jason Wang <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Paolo Abeni <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: HarshaVardhana S A <[email protected]>
Date:   Tue Jul 1 14:22:54 2025 +0200

    vsock/vmci: Clear the vmci transport packet properly when initializing it
    
    commit 223e2288f4b8c262a864e2c03964ffac91744cd5 upstream.
    
    In vmci_transport_packet_init memset the vmci_transport_packet before
    populating the fields to avoid any uninitialised data being left in the
    structure.
    
    Cc: Bryan Tan <[email protected]>
    Cc: Vishnu Dasa <[email protected]>
    Cc: Broadcom internal kernel review list
    Cc: Stefano Garzarella <[email protected]>
    Cc: "David S. Miller" <[email protected]>
    Cc: Eric Dumazet <[email protected]>
    Cc: Jakub Kicinski <[email protected]>
    Cc: Paolo Abeni <[email protected]>
    Cc: Simon Horman <[email protected]>
    Cc: [email protected]
    Cc: [email protected]
    Cc: stable <[email protected]>
    Signed-off-by: HarshaVardhana S A <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>
    Fixes: d021c344051a ("VSOCK: Introduce VM Sockets")
    Acked-by: Stefano Garzarella <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Paolo Abeni <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Johannes Berg <[email protected]>
Date:   Tue Jun 17 11:45:29 2025 +0200

    wifi: ath6kl: remove WARN on bad firmware input
    
    [ Upstream commit e7417421d89358da071fd2930f91e67c7128fbff ]
    
    If the firmware gives bad input, that's nothing to do with
    the driver's stack at this point etc., so the WARN_ON()
    doesn't add any value. Additionally, this is one of the
    top syzbot reports now. Just print a message, and as an
    added bonus, print the sizes too.
    
    Reported-by: [email protected]
    Tested-by: [email protected]
    Acked-by: Jeff Johnson <[email protected]>
    Link: https://patch.msgid.link/20250617114529.031a677a348e.I58bf1eb4ac16a82c546725ff010f3f0d2b0cca49@changeid
    Signed-off-by: Johannes Berg <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Muna Sinada <[email protected]>
Date:   Tue Mar 25 14:31:23 2025 -0700

    wifi: mac80211: Add link iteration macro for link data
    
    [ Upstream commit f61c7b3d442bef91dd432d468d08f72eadcc3209 ]
    
    Currently before iterating through valid links we are utilizing
    open-coding when checking if vif valid_links is a non-zero value.
    
    Add new macro, for_each_link_data(), which iterates through link_id
    and checks if it is set on vif valid_links. If it is a valid link then
    access link data for that link id.
    
    Signed-off-by: Muna Sinada <[email protected]>
    Link: https://patch.msgid.link/[email protected]
    Signed-off-by: Johannes Berg <[email protected]>
    Stable-dep-of: d87c3ca0f8f1 ("wifi: mac80211: finish link init before RCU publish")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Johannes Berg <[email protected]>
Date:   Mon Jan 29 19:34:39 2024 +0100

    wifi: mac80211: chan: chandef is non-NULL for reserved
    
    [ Upstream commit 9bf7079bc2271321fac467cae981c44e495b76b9 ]
    
    The last caller of this with a NULL argument was related to
    the non-chanctx code, so we can now remove this odd logic.
    
    Reviewed-by: Miriam Rachel Korenblit <[email protected]>
    Link: https://msgid.link/20240129194108.bad8ec1e76c8.I12287452f42c54baf75821e75491cf6d021af20a@changeid
    Signed-off-by: Johannes Berg <[email protected]>
    Stable-dep-of: d87c3ca0f8f1 ("wifi: mac80211: finish link init before RCU publish")
    Signed-off-by: Sasha Levin <[email protected]>

Author: Johannes Berg <[email protected]>
Date:   Mon Jun 16 17:18:38 2025 +0200

    wifi: mac80211: drop invalid source address OCB frames
    
    [ Upstream commit d1b1a5eb27c4948e8811cf4dbb05aaf3eb10700c ]
    
    In OCB, don't accept frames from invalid source addresses
    (and in particular don't try to create stations for them),
    drop the frames instead.
    
    Reported-by: [email protected]
    Closes: https://lore.kernel.org/r/[email protected]/
    Signed-off-by: Johannes Berg <[email protected]>
    Tested-by: [email protected]
    Link: https://patch.msgid.link/20250616171838.7433379cab5d.I47444d63c72a0bd58d2e2b67bb99e1fea37eec6f@changeid
    Signed-off-by: Johannes Berg <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Johannes Berg <[email protected]>
Date:   Tue Jun 24 13:07:49 2025 +0200

    wifi: mac80211: finish link init before RCU publish
    
    [ Upstream commit d87c3ca0f8f1ca4c25f2ed819e954952f4d8d709 ]
    
    Since the link/conf pointers can be accessed without any
    protection other than RCU, make sure the data is actually
    set up before publishing the structures.
    
    Fixes: b2e8434f1829 ("wifi: mac80211: set up/tear down client vif links properly")
    Link: https://patch.msgid.link/20250624130749.9a308b713c74.I4a80f5eead112a38730939ea591d2e275c721256@changeid
    Signed-off-by: Johannes Berg <[email protected]>
    Signed-off-by: Sasha Levin <[email protected]>

Author: Borislav Petkov (AMD) <[email protected]>
Date:   Wed Sep 11 10:53:08 2024 +0200

    x86/bugs: Add a Transient Scheduler Attacks mitigation
    
    Commit d8010d4ba43e9f790925375a7de100604a5e2dba upstream.
    
    Add the required features detection glue to bugs.c et all in order to
    support the TSA mitigation.
    
    Co-developed-by: Kim Phillips <[email protected]>
    Signed-off-by: Kim Phillips <[email protected]>
    Signed-off-by: Borislav Petkov (AMD) <[email protected]>
    Reviewed-by: Pawan Gupta <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Borislav Petkov (AMD) <[email protected]>
Date:   Wed Sep 11 05:13:46 2024 +0200

    x86/bugs: Rename MDS machinery to something more generic
    
    Commit f9af88a3d384c8b55beb5dc5483e5da0135fadbd upstream.
    
    It will be used by other x86 mitigations.
    
    No functional changes.
    
    Signed-off-by: Borislav Petkov (AMD) <[email protected]>
    Reviewed-by: Pawan Gupta <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Borislav Petkov (AMD) <[email protected]>
Date:   Thu Mar 27 12:23:55 2025 +0100

    x86/microcode/AMD: Add TSA microcode SHAs
    
    Commit 2329f250e04d3b8e78b36a68b9880ca7750a07ef upstream.
    
    Signed-off-by: Borislav Petkov (AMD) <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Borislav Petkov (AMD) <[email protected]>
Date:   Mon Apr 14 15:33:19 2025 +0200

    x86/process: Move the buffer clearing before MONITOR
    
    Commit 8e786a85c0a3c0fffae6244733fb576eeabd9dec upstream.
    
    Move the VERW clearing before the MONITOR so that VERW doesn't disarm it
    and the machine never enters C1.
    
    Original idea by Kim Phillips <[email protected]>.
    
    Suggested-by: Andrew Cooper <[email protected]>
    Signed-off-by: Borislav Petkov (AMD) <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Xin Li (Intel) <[email protected]>
Date:   Sun Jul 6 07:43:08 2025 -0400

    x86/traps: Initialize DR6 by writing its architectural reset value
    
    [ Upstream commit 5f465c148c61e876b6d6eacd8e8e365f2d47758f ]
    
    Initialize DR6 by writing its architectural reset value to avoid
    incorrectly zeroing DR6 to clear DR6.BLD at boot time, which leads
    to a false bus lock detected warning.
    
    The Intel SDM says:
    
      1) Certain debug exceptions may clear bits 0-3 of DR6.
    
      2) BLD induced #DB clears DR6.BLD and any other debug exception
         doesn't modify DR6.BLD.
    
      3) RTM induced #DB clears DR6.RTM and any other debug exception
         sets DR6.RTM.
    
      To avoid confusion in identifying debug exceptions, debug handlers
      should set DR6.BLD and DR6.RTM, and clear other DR6 bits before
      returning.
    
    The DR6 architectural reset value 0xFFFF0FF0, already defined as
    macro DR6_RESERVED, satisfies these requirements, so just use it to
    reinitialize DR6 whenever needed.
    
    Since clear_all_debug_regs() no longer zeros all debug registers,
    rename it to initialize_debug_regs() to better reflect its current
    behavior.
    
    Since debug_read_clear_dr6() no longer clears DR6, rename it to
    debug_read_reset_dr6() to better reflect its current behavior.
    
    Fixes: ebb1064e7c2e9 ("x86/traps: Handle #DB for bus lock")
    Reported-by: Sohil Mehta <[email protected]>
    Suggested-by: H. Peter Anvin (Intel) <[email protected]>
    Signed-off-by: Xin Li (Intel) <[email protected]>
    Signed-off-by: Dave Hansen <[email protected]>
    Reviewed-by: H. Peter Anvin (Intel) <[email protected]>
    Reviewed-by: Sohil Mehta <[email protected]>
    Acked-by: Peter Zijlstra (Intel) <[email protected]>
    Tested-by: Sohil Mehta <[email protected]>
    Link: https://lore.kernel.org/lkml/[email protected]/
    Cc:[email protected]
    Link: https://lore.kernel.org/all/20250620231504.2676902-2-xin%40zytor.com
    Signed-off-by: Sasha Levin <[email protected]>

Author: Mathias Nyman <[email protected]>
Date:   Fri Jun 27 17:41:22 2025 +0300

    xhci: dbc: Flush queued requests before stopping dbc
    
    commit efe3e3ae5a66cb38ef29c909e951b4039044bae9 upstream.
    
    Flush dbc requests when dbc is stopped and transfer rings are freed.
    Failure to flush them lead to leaking memory and dbc completing odd
    requests after resuming from suspend, leading to error messages such as:
    
    [   95.344392] xhci_hcd 0000:00:0d.0: no matched request
    
    Cc: stable <[email protected]>
    Fixes: dfba2174dc42 ("usb: xhci: Add DbC support in xHCI driver")
    Signed-off-by: Mathias Nyman <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Łukasz Bartosik <[email protected]>
Date:   Fri Jun 27 17:41:21 2025 +0300

    xhci: dbctty: disable ECHO flag by default
    
    commit 2b857d69a5e116150639a0c6c39c86cc329939ee upstream.
    
    When /dev/ttyDBC0 device is created then by default ECHO flag
    is set for the terminal device. However if data arrives from
    a peer before application using /dev/ttyDBC0 applies its set
    of terminal flags then the arriving data will be echoed which
    might not be desired behavior.
    
    Fixes: 4521f1613940 ("xhci: dbctty: split dbc tty driver registration and unregistration functions.")
    Cc: stable <[email protected]>
    Signed-off-by: Łukasz Bartosik <[email protected]>
    Signed-off-by: Mathias Nyman <[email protected]>
    Link: https://lore.kernel.org/stable/20250610111802.18742-1-ukaszb%40chromium.org
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>

Author: Hongyu Xie <[email protected]>
Date:   Fri Jun 27 17:41:20 2025 +0300

    xhci: Disable stream for xHC controller with XHCI_BROKEN_STREAMS
    
    commit cd65ee81240e8bc3c3119b46db7f60c80864b90b upstream.
    
    Disable stream for platform xHC controller with broken stream.
    
    Fixes: 14aec589327a6 ("storage: accept some UAS devices if streams are unavailable")
    Cc: stable <[email protected]>
    Signed-off-by: Hongyu Xie <[email protected]>
    Signed-off-by: Mathias Nyman <[email protected]>
    Link: https://lore.kernel.org/r/[email protected]
    Signed-off-by: Greg Kroah-Hartman <[email protected]>