Changelog in Linux kernel 6.11.1

 
accel: Use XArray instead of IDR for minors [+ + +]
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Fri Aug 23 18:30:47 2024 +0200

    accel: Use XArray instead of IDR for minors
    
    [ Upstream commit 45c4d994b82b08f0ce5eb50f8da29379c92a391e ]
    
    Accel minor management is based on DRM (and is also using struct
    drm_minor internally), since DRM is using XArray for minors, it makes
    sense to also convert accel.
    As the two implementations are identical (only difference being the
    underlying xarray), move the accel_minor_* functionality to DRM.
    
    Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
    Acked-by: James Zhu <James.Zhu@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20240823163048.2676257-3-michal.winiarski@intel.com
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
ASoC: amd: acp: add ZSC control register programming sequence [+ + +]
Author: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Date:   Wed Aug 7 14:21:48 2024 +0530

    ASoC: amd: acp: add ZSC control register programming sequence
    
    commit c35fad6f7e0d69b0e9e7e196bdbca3ed03ac24ea upstream.
    
    Add ZSC Control register programming sequence for ACP D0 and D3 state
    transitions for ACP7.0 onwards. This will allow ACP to enter low power
    state when ACP enters D3 state. When ACP enters D0 State, ZSC control
    should be disabled.
    
    Tested-by: Leo Li <sunpeng.li@amd.com>
    Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
    Link: https://patch.msgid.link/20240807085154.1987681-1-Vijendar.Mukunda@amd.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
Bluetooth: btintel_pcie: Allocate memory for driver private data [+ + +]
Author: Kiran K <kiran.k@intel.com>
Date:   Thu Sep 12 16:21:00 2024 +0530

    Bluetooth: btintel_pcie: Allocate memory for driver private data
    
    commit 7ffaa200251871980af12e57649ad57c70bf0f43 upstream.
    
    Fix driver not allocating memory for struct btintel_data which is used
    to store internal data.
    
    Fixes: 6e65a09f9275 ("Bluetooth: btintel_pcie: Add *setup* function to download firmware")
    Signed-off-by: Kiran K <kiran.k@intel.com>
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Cc: Thomas Leroy <thomas.leroy@suse.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
cpufreq/amd-pstate: Add the missing cpufreq_cpu_put() [+ + +]
Author: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
Date:   Fri Aug 9 06:08:16 2024 +0000

    cpufreq/amd-pstate: Add the missing cpufreq_cpu_put()
    
    [ Upstream commit 49243adc715e6ae34d6cc003827e63bcf5b3a21d ]
    
    Fix the reference counting of cpufreq_policy object in amd_pstate_update()
    function by adding the missing cpufreq_cpu_put().
    
    Fixes: e8f555daacd3 ("cpufreq/amd-pstate: fix setting policy current frequency value")
    Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
    Reviewed-by: Perry Yuan <perry.yuan@amd.com>
    Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
drm: Expand max DRM device number to full MINORBITS [+ + +]
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Fri Aug 23 18:30:48 2024 +0200

    drm: Expand max DRM device number to full MINORBITS
    
    [ Upstream commit 071d583e01c88272f6ff216d4f867f8f35e94d7d ]
    
    Having a limit of 64 DRM devices is not good enough for modern world
    where we have multi-GPU servers, SR-IOV virtual functions and virtual
    devices used for testing.
    Let's utilize full minor range for DRM devices.
    To avoid regressing the existing userspace, we're still maintaining the
    numbering scheme where 0-63 is used for primary, 64-127 is reserved
    (formerly for control) and 128-191 is used for render.
    For minors >= 192, we're allocating minors dynamically on a first-come,
    first-served basis.
    
    Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20240823163048.2676257-4-michal.winiarski@intel.com
    Acked-by: James Zhu <James.Zhu@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

drm: Use XArray instead of IDR for minors [+ + +]
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Fri Aug 23 18:30:46 2024 +0200

    drm: Use XArray instead of IDR for minors
    
    [ Upstream commit 5fbca8b48b3050ae7fb611a8b09af60012ed6de1 ]
    
    IDR is deprecated, and since XArray manages its own state with internal
    locking, it simplifies the locking on DRM side.
    Additionally, don't use the IRQ-safe variant, since operating on drm
    minor is not done in IRQ context.
    
    Suggested-by: Matthew Wilcox <willy@infradead.org>
    Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
    Acked-by: James Zhu <James.Zhu@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20240823163048.2676257-2-michal.winiarski@intel.com
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
 
Linux: Linux 6.11.1 [+ + +]
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Mon Sep 30 16:31:09 2024 +0200

    Linux 6.11.1
    
    Link: https://lore.kernel.org/r/20240927121715.213013166@linuxfoundation.org
    Tested-by: Ronald Warsow <rwarsow@gmx.de>
    Tested-by: Peter Schneider <pschneider1968@googlemail.com>
    Tested-by: Jon Hunter <jonathanh@nvidia.com>
    Tested-by: Justin M. Forbes <jforbes@fedoraproject.org>
    Tested-by: Christian Heusel <christian@heusel.eu>
    Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
    Tested-by: Salvatore Bonaccorso <carnil@debian.org>
    Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
    Tested-by: Allen Pais <apais@linux.microsoft.com>
    Tested-by: Shuah Khan <skhan@linuxfoundation.org>
    Tested-by: Ron Economos <re@w6rz.net>
    Tested-by: Kexy Biscuit <kexybiscuit@aosc.io>
    Tested-by: kernelci.org bot <bot@kernelci.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
netfilter: nft_socket: Fix a NULL vs IS_ERR() bug in nft_socket_cgroup_subtree_level() [+ + +]
Author: Dan Carpenter <dan.carpenter@linaro.org>
Date:   Sat Sep 14 12:56:51 2024 +0300

    netfilter: nft_socket: Fix a NULL vs IS_ERR() bug in nft_socket_cgroup_subtree_level()
    
    commit 7052622fccb1efb850c6b55de477f65d03525a30 upstream.
    
    The cgroup_get_from_path() function never returns NULL, it returns error
    pointers.  Update the error handling to match.
    
    Fixes: 7f3287db6543 ("netfilter: nft_socket: make cgroupsv2 matching work with namespaces")
    Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
    Acked-by: Florian Westphal <fw@strlen.de>
    Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
    Link: https://patch.msgid.link/bbc0c4e0-05cc-4f44-8797-2f4b3920a820@stanley.mountain
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
nvme-pci: qdepth 1 quirk [+ + +]
Author: Keith Busch <kbusch@kernel.org>
Date:   Wed Sep 11 10:39:59 2024 -0700

    nvme-pci: qdepth 1 quirk
    
    commit 83bdfcbdbe5d901c5fa432decf12e1725a840a56 upstream.
    
    Another device has been reported to be unreliable if we have more than
    one outstanding command. In this new case, data corruption may occur.
    Since we have two devices now needing this quirky behavior, make a
    generic quirk flag.
    
    The same Apple quirk is clearly not "temporary", so update the comment
    while moving it.
    
    Link: https://lore.kernel.org/linux-nvme/191d810a4e3.fcc6066c765804.973611676137075390@collabora.com/
    Reported-by: Robert Beckett <bob.beckett@collabora.com>
    Reviewed-by: Christoph Hellwig hch@lst.de>
    Signed-off-by: Keith Busch <kbusch@kernel.org>
    Cc: "Gagniuc, Alexandru" <alexandru.gagniuc@hp.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
powercap/intel_rapl: Add support for AMD family 1Ah [+ + +]
Author: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
Date:   Fri Jul 19 10:12:35 2024 +0000

    powercap/intel_rapl: Add support for AMD family 1Ah
    
    [ Upstream commit 166df51097a258a14fe9e946e2157f3b75eeb3c2 ]
    
    AMD Family 1Ah's RAPL MSRs are identical to Family 19h's,
    extend Family 19h's support to Family 1Ah.
    
    Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
    Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
    Link: https://patch.msgid.link/20240719101234.50827-1-Dhananjay.Ugwekar@amd.com
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

powercap/intel_rapl: Fix the energy-pkg event for AMD CPUs [+ + +]
Author: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
Date:   Tue Jul 30 04:49:19 2024 +0000

    powercap/intel_rapl: Fix the energy-pkg event for AMD CPUs
    
    [ Upstream commit 26096aed255fbac9501718174dbb24c935d8854e ]
    
    After commit ("x86/cpu/topology: Add support for the AMD 0x80000026 leaf"),
    on AMD processors that support extended CPUID leaf 0x80000026, the
    topology_logical_die_id() macros, no longer returns package id, instead it
    returns the CCD (Core Complex Die) id. This leads to the energy-pkg
    event scope to be modified to CCD instead of package.
    
    For more historical context, please refer to commit 32fb480e0a2c
    ("powercap/intel_rapl: Support multi-die/package"), which initially changed
    the RAPL scope from package to die for all systems, as Intel systems
    with Die enumeration have RAPL scope as die, and those without die
    enumeration are not affected. So, all systems(Intel, AMD, Hygon), worked
    correctly with topology_logical_die_id() until recently, but this changed
    after the "0x80000026 leaf" commit mentioned above.
    
    Future multi-die Intel systems will have package scope RAPL counters,
    but they will be using TPMI RAPL interface, which is not affected by
    this change.
    
    Replacing topology_logical_die_id() with topology_physical_package_id()
    conditionally only for AMD and Hygon fixes the energy-pkg event.
    
    On an AMD 2 socket 8 CCD Zen4 server:
    
    Before:
    
    linux$ ls /sys/class/powercap/
    intel-rapl      intel-rapl:4    intel-rapl:8:0  intel-rapl:d
    intel-rapl:0    intel-rapl:4:0  intel-rapl:9    intel-rapl:d:0
    intel-rapl:0:0  intel-rapl:5    intel-rapl:9:0  intel-rapl:e
    intel-rapl:1    intel-rapl:5:0  intel-rapl:a    intel-rapl:e:0
    intel-rapl:1:0  intel-rapl:6    intel-rapl:a:0  intel-rapl:f
    intel-rapl:2    intel-rapl:6:0  intel-rapl:b    intel-rapl:f:0
    intel-rapl:2:0  intel-rapl:7    intel-rapl:b:0
    intel-rapl:3    intel-rapl:7:0  intel-rapl:c
    intel-rapl:3:0  intel-rapl:8    intel-rapl:c:0
    
    After:
    
    linux$ ls /sys/class/powercap/
    intel-rapl  intel-rapl:0  intel-rapl:0:0  intel-rapl:1  intel-rapl:1:0
    
    Only one sysfs entry per-event per-package is created after this change.
    
    Fixes: 63edbaa48a57 ("x86/cpu/topology: Add support for the AMD 0x80000026 leaf")
    Reported-by: Michael Larabel <michael@michaellarabel.com>
    Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
    Reviewed-by: Zhang Rui <rui.zhang@intel.com>
    Link: https://patch.msgid.link/20240730044917.4680-3-Dhananjay.Ugwekar@amd.com
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 
powercap: intel_rapl: Change an error pointer to NULL [+ + +]
Author: Dan Carpenter <dan.carpenter@linaro.org>
Date:   Fri Aug 23 15:51:36 2024 +0300

    powercap: intel_rapl: Change an error pointer to NULL
    
    commit 6b08b4ee5e60d8789aeb87250f718ef14bebb90e upstream.
    
    The rapl_find_package_domain_cpuslocked() function is supposed to
    return NULL on error.
    
    This new error patch returns ERR_PTR(-EINVAL) but none of the callers
    check for that so it would lead to an Oops.
    
    Fixes: 26096aed255f ("powercap/intel_rapl: Fix the energy-pkg event for AMD CPUs")
    Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
    Link: https://patch.msgid.link/fa719c6a-8d3b-4cca-9b43-bcd477ff6655@stanley.mountain
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

 
USB: serial: pl2303: add device id for Macrosilicon MS3020 [+ + +]
Author: Junhao Xie <bigfoot@classfun.cn>
Date:   Tue Sep 3 23:06:38 2024 +0800

    USB: serial: pl2303: add device id for Macrosilicon MS3020
    
    commit 7d47d22444bb7dc1b6d768904a22070ef35e1fc0 upstream.
    
    Add the device id for the Macrosilicon MS3020 which is a
    PL2303HXN based device.
    
    Signed-off-by: Junhao Xie <bigfoot@classfun.cn>
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

USB: usbtmc: prevent kernel-usb-infoleak [+ + +]
Author: Edward Adam Davis <eadavis@qq.com>
Date:   Sun Sep 8 17:17:41 2024 +0800

    USB: usbtmc: prevent kernel-usb-infoleak
    
    commit 625fa77151f00c1bd00d34d60d6f2e710b3f9aad upstream.
    
    The syzbot reported a kernel-usb-infoleak in usbtmc_write,
    we need to clear the structure before filling fields.
    
    Fixes: 4ddc645f40e9 ("usb: usbtmc: Add ioctl for vendor specific write")
    Reported-and-tested-by: syzbot+9d34f80f841e948c3fdb@syzkaller.appspotmail.com
    Closes: https://syzkaller.appspot.com/bug?extid=9d34f80f841e948c3fdb
    Signed-off-by: Edward Adam Davis <eadavis@qq.com>
    Cc: stable <stable@kernel.org>
    Link: https://lore.kernel.org/r/tencent_9649AA6EC56EDECCA8A7D106C792D1C66B06@qq.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>