[PATCH 6.17 00/60] 6.17.12-rc1 review

[PATCH 6.17 00/60] 6.17.12-rc1 review

[Greg Kroah-Hartman]

This is the start of the stable review cycle for the 6.17.12 release.
There are 60 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Fri, 12 Dec 2025 07:29:37 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.12-rc1.gz
or in the git tree and branch at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
and the diffstat can be found below.

thanks,

greg k-h

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Linux 6.17.12-rc1

Navaneeth K <knavaneeth786@gmail.com>
    staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing

Navaneeth K <knavaneeth786@gmail.com>
    staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing

Navaneeth K <knavaneeth786@gmail.com>
    staging: rtl8723bs: fix out-of-bounds read in rtw_get_ie() parser

Nikita Zhandarovich <n.zhandarovich@fintech.ru>
    comedi: check device's attached status in compat ioctls

Nikita Zhandarovich <n.zhandarovich@fintech.ru>
    comedi: multiq3: sanitize config options in multiq3_attach()

Ian Abbott <abbotti@mev.co.uk>
    comedi: c6xdigio: Fix invalid PNP driver unregistration

Antoniu Miclaus <antoniu.miclaus@analog.com>
    iio: adc: ad4080: fix chip identification

Zenm Chen <zenmchen@gmail.com>
    wifi: rtw88: Add USB ID 2001:3329 for D-Link AC13U rev. A1

Zenm Chen <zenmchen@gmail.com>
    wifi: rtl8xxxu: Add USB ID 2001:3328 for D-Link AN3U rev. A1

Marcos Vega <marcosmola2@gmail.com>
    platform/x86: hp-wmi: Add Omen MAX 16-ah0xx fan support and thermal profile

Krishna Chomal <krishna.chomal108@gmail.com>
    platform/x86: hp-wmi: Add Omen 16-wf1xxx fan support

Linus Torvalds <torvalds@linux-foundation.org>
    samples: work around glibc redefining some of our defines wrong

Huacai Chen <chenhuacai@kernel.org>
    LoongArch: Mask all interrupts during kexec/kdump

Zqiang <qiang.zhang@linux.dev>
    sched_ext: Use IRQ_WORK_INIT_HARD() to initialize rq->scx.kick_cpus_irq_work

Naoki Ueki <naoki25519@gmail.com>
    HID: elecom: Add support for ELECOM M-XT3URBK (018F)

Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
    platform/x86/intel/hid: Add Nova Lake support

Zqiang <qiang.zhang@linux.dev>
    sched_ext: Fix possible deadlock in the deferred_irq_workfn()

Antheas Kapenekakis <lkml@antheas.dev>
    platform/x86/amd/pmc: Add spurious_8042 to Xbox Ally

Antheas Kapenekakis <lkml@antheas.dev>
    platform/x86/amd: pmc: Add Lenovo Legion Go 2 to pmc quirk list

Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
    platform/x86: intel-uncore-freq: Add additional client processors

Jia Ston <ston.jia@outlook.com>
    platform/x86: huawei-wmi: add keys for HONOR models

April Grimoire <april@aprilg.moe>
    HID: apple: Add SONiX AK870 PRO to non_apple_keyboards quirk list

Armin Wolf <W_Armin@gmx.de>
    platform/x86: acer-wmi: Ignore backlight event

Praveen Talari <praveen.talari@oss.qualcomm.com>
    pinctrl: qcom: msm: Fix deadlock in pinmux configuration

Keith Busch <kbusch@kernel.org>
    nvme: fix admin request_queue lifetime

Edip Hazuri <edip@medip.dev>
    platform/x86: hp-wmi: mark Victus 16-r0 and 16-s0 for victus_s fan and thermal profile support

Antheas Kapenekakis <lkml@antheas.dev>
    platform/x86/amd/pmc: Add support for Van Gogh SoC

Mario Limonciello (AMD) <superm1@kernel.org>
    HID: hid-input: Extend Elan ignore battery quirk to USB

Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    bfs: Reconstruct file type when loading from disk

Lauri Tirkkonen <lauri@hacktheplanet.fi>
    HID: lenovo: fixup Lenovo Yoga Slim 7x Keyboard rdesc

Lushih Hsieh <bruce@mail.kh.edu.tw>
    ALSA: usb-audio: Add native DSD quirks for PureAudio DAC series

Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>
    drm/amdkfd: Fix GPU mappings for APU after prefetch

Yiqi Sun <sunyiqixm@gmail.com>
    smb: fix invalid username check in smb3_fs_context_parse_param()

Niranjan H Y <niranjan.hy@ti.com>
    ASoC: SDCA: bug fix while parsing mipi-sdca-control-cn-list

Max Chou <max.chou@realtek.com>
    Bluetooth: btrtl: Avoid loading the config file on security chips

Baojun Xu <baojun.xu@ti.com>
    ALSA: hda/tas2781: Add new quirk for HP new projects

Adrian Barnaś <abarnas@google.com>
    arm64: Reject modules with internal alternative callbacks

Ian Forbes <ian.forbes@broadcom.com>
    drm/vmwgfx: Use kref in vmw_bo_dirty

Kaushlendra Kumar <kaushlendra.kumar@intel.com>
    ACPI: MRRM: Fix memory leaks and improve error handling

Robin Gong <yibin.gong@nxp.com>
    spi: imx: keep dma request disabled before dma transfer setup

Alvaro Gamez Machado <alvaro.gamez@hazent.com>
    spi: xilinx: increase number of retries before declaring stall

Song Liu <song@kernel.org>
    ftrace: bpf: Fix IPMODIFY + DIRECT in modify_ftrace_direct()

Johan Hovold <johan@kernel.org>
    USB: serial: kobil_sct: fix TIOCMBIS and TIOCMBIC

Johan Hovold <johan@kernel.org>
    USB: serial: belkin_sa: fix TIOCMBIS and TIOCMBIC

Biju Das <biju.das.jz@bp.renesas.com>
    serial: sh-sci: Fix deadlock during RSCI FIFO overrun error

Biju Das <biju.das.jz@bp.renesas.com>
    dt-bindings: serial: rsci: Drop "uart-has-rtscts: false"

Magne Bruno <magne.bruno@addi-data.com>
    serial: add support of CPCI cards

Johan Hovold <johan@kernel.org>
    USB: serial: ftdi_sio: match on interface number for jtag

Fabio Porcedda <fabio.porcedda@gmail.com>
    USB: serial: option: move Telit 0x10c7 composition in the right place

Fabio Porcedda <fabio.porcedda@gmail.com>
    USB: serial: option: add Telit Cinterion FE910C04 new compositions

Slark Xiao <slark_xiao@163.com>
    USB: serial: option: add Foxconn T99W760

Omar Sandoval <osandov@fb.com>
    KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced

Nikita Zhandarovich <n.zhandarovich@fintech.ru>
    comedi: pcl818: fix null-ptr-deref in pcl818_ai_cancel()

Alexey Nepomnyashih <sdl@nppct.ru>
    ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock()

Giovanni Cabiddu <giovanni.cabiddu@intel.com>
    crypto: zstd - fix double-free in per-CPU stream cleanup

Alexander Sverdlin <alexander.sverdlin@gmail.com>
    locking/spinlock/debug: Fix data-race in do_raw_write_lock

Qianchang Zhao <pioooooooooip@gmail.com>
    ksmbd: ipc: fix use-after-free in ipc_msg_send_request

Deepanshu Kartikey <kartikey406@gmail.com>
    ext4: refresh inline data size before write operations

Ye Bin <yebin10@huawei.com>
    jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted

Bagas Sanjaya <bagasdotme@gmail.com>
    Documentation: process: Also mention Sasha Levin as stable tree maintainer


-------------

Diffstat:

 .../devicetree/bindings/serial/renesas,rsci.yaml   |  2 -
 Documentation/process/2.Process.rst                |  6 +-
 Makefile                                           |  4 +-
 arch/arm64/include/asm/alternative.h               |  7 ++-
 arch/arm64/kernel/alternative.c                    | 19 +++---
 arch/arm64/kernel/module.c                         |  9 ++-
 arch/loongarch/kernel/machine_kexec.c              |  2 +
 arch/x86/include/asm/kvm_host.h                    |  9 +++
 arch/x86/kvm/svm/svm.c                             | 24 ++++----
 arch/x86/kvm/x86.c                                 | 21 +++++++
 crypto/zstd.c                                      |  7 +--
 drivers/acpi/acpi_mrrm.c                           | 51 ++++++++++-----
 drivers/bluetooth/btrtl.c                          | 24 ++++----
 drivers/comedi/comedi_fops.c                       | 42 +++++++++++--
 drivers/comedi/drivers/c6xdigio.c                  | 46 ++++++++++----
 drivers/comedi/drivers/multiq3.c                   |  9 +++
 drivers/comedi/drivers/pcl818.c                    |  5 +-
 drivers/gpu/drm/amd/amdkfd/kfd_svm.c               |  2 +
 drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c         | 12 ++--
 drivers/hid/hid-apple.c                            |  1 +
 drivers/hid/hid-elecom.c                           |  6 +-
 drivers/hid/hid-ids.h                              |  4 +-
 drivers/hid/hid-input.c                            |  5 +-
 drivers/hid/hid-lenovo.c                           | 17 +++++
 drivers/hid/hid-quirks.c                           |  3 +-
 drivers/iio/adc/ad4080.c                           |  9 ++-
 drivers/net/wireless/realtek/rtl8xxxu/core.c       |  3 +
 drivers/net/wireless/realtek/rtw88/rtw8822cu.c     |  2 +
 drivers/nvme/host/core.c                           |  3 +-
 drivers/pinctrl/qcom/pinctrl-msm.c                 |  2 +-
 drivers/platform/x86/acer-wmi.c                    |  4 ++
 drivers/platform/x86/amd/pmc/pmc-quirks.c          | 25 ++++++++
 drivers/platform/x86/amd/pmc/pmc.c                 |  3 +
 drivers/platform/x86/amd/pmc/pmc.h                 |  1 +
 drivers/platform/x86/hp/hp-wmi.c                   |  6 +-
 drivers/platform/x86/huawei-wmi.c                  |  4 ++
 drivers/platform/x86/intel/hid.c                   |  1 +
 .../x86/intel/uncore-frequency/uncore-frequency.c  |  4 ++
 drivers/spi/spi-imx.c                              | 15 +++--
 drivers/spi/spi-xilinx.c                           |  2 +-
 drivers/staging/rtl8723bs/core/rtw_ieee80211.c     | 14 +++--
 drivers/staging/rtl8723bs/core/rtw_mlme_ext.c      | 13 ++--
 drivers/tty/serial/8250/8250_pci.c                 | 37 +++++++++++
 drivers/tty/serial/sh-sci.c                        | 12 +++-
 drivers/usb/serial/belkin_sa.c                     | 28 +++++----
 drivers/usb/serial/ftdi_sio.c                      | 72 ++++++++--------------
 drivers/usb/serial/kobil_sct.c                     | 18 +++---
 drivers/usb/serial/option.c                        | 22 ++++++-
 fs/bfs/inode.c                                     | 19 +++++-
 fs/ext4/inline.c                                   | 14 ++++-
 fs/jbd2/transaction.c                              | 19 ++++--
 fs/smb/client/fs_context.c                         |  2 +-
 fs/smb/server/transport_ipc.c                      |  7 ++-
 kernel/locking/spinlock_debug.c                    |  4 +-
 kernel/sched/ext.c                                 |  4 +-
 kernel/trace/ftrace.c                              | 40 +++++++++---
 samples/vfs/test-statx.c                           |  6 ++
 samples/watch_queue/watch_test.c                   |  6 ++
 sound/hda/codecs/realtek/alc269.c                  |  9 +++
 sound/soc/sdca/sdca_functions.c                    |  3 +-
 sound/usb/quirks.c                                 |  6 ++
 61 files changed, 564 insertions(+), 212 deletions(-)

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Brett A C Sheffield]

# Librecast Test Results

020/020 [ OK ] liblcrq
010/010 [ OK ] libmld
120/120 [ OK ] liblibrecast

CPU/kernel: Linux auntie 6.17.12-rc1-ge7c0ca6d291c #1 SMP PREEMPT_DYNAMIC Wed Dec 10 10:02:01 -00 2025 x86_64 AMD Ryzen 9 9950X 16-Core Processor AuthenticAMD GNU/Linux

Tested-by: Brett A C Sheffield <bacs@librecast.net>

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Jeffrin Thalakkottoor]

 compiled and booted 6.17.12-rc1+
Version: AMD A4-4000 APU with Radeon(tm) HD Graphics

sudo dmesg -l errr  shows  error

j$sudo dmesg -l err
[   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
$

Tested-by: Jeffrin Jose T <jeffrin@rajagiritech.edu.in>

--
software engineer
rajagiri school of engineering and technology

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Achill Gilgenast]

On Wed Dec 10, 2025 at 8:29 AM CET, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 12 Dec 2025 07:29:37 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.12-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Thank you! Build tested on all Alpine architectures and boot tested on
x86_64.

Tested-By: Achill Gilgenast <achill@achill.org>

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Greg Kroah-Hartman]

On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
>  compiled and booted 6.17.12-rc1+
> Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> 
> sudo dmesg -l errr  shows  error
> 
> j$sudo dmesg -l err
> [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> $

Is ths new?  if so, can you bisect?

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Peter Schneider]

Am 10.12.2025 um 08:29 schrieb Greg Kroah-Hartman:
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.

Builds, boots and works on my 2-socket Ivy Bridge Xeon E5-2697 v2 server. No dmesg oddities or regressions found.

Tested-by: Peter Schneider <pschneider1968@googlemail.com>


Beste Grüße,
Peter Schneider

-- 
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you.                    -- David McCullough Jr.

OpenPGP:  0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Jeffrin Thalakkottoor]

On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
> >  compiled and booted 6.17.12-rc1+
> > Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> >
> > sudo dmesg -l errr  shows  error
> >
> > j$sudo dmesg -l err
> > [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> > $
>
> Is ths new?  if so, can you bisect?

this is new related. Previous stable release err and warn disappeared
(i think i changed  .config)

can you give me a  step by step tutorial  for git bisect


t


-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Brett A C Sheffield]

On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
> > >  compiled and booted 6.17.12-rc1+
> > > Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> > >
> > > sudo dmesg -l errr  shows  error
> > >
> > > j$sudo dmesg -l err
> > > [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> > > $
> >
> > Is ths new?  if so, can you bisect?
> 
> this is new related. Previous stable release err and warn disappeared
> (i think i changed  .config)
> 
> can you give me a  step by step tutorial  for git bisect

1) cd to wherever you have your kernel checked out

2) `git bisect start`

3) if you're already on a known-bad commit, then mark it as such:

  `git bisect bad`

4) Mark the last known good commit as such:

  `git bisect good <commit / tag>`

git bisect will choose a commit to test.

5) Build, install and boot your kernel as you usually do

6) Run whatever test you need to determine if the booted kernel is good or bad
(check dmesg in this case)

7) Mark the commit as good or bad. Git will choose another commit for you.

8) Goto 5.

`git help bisect` will give you more information.

At the end of the process git will tell you the first bad commit found.  You can
dump the bisection log with:

`git bisect log`

which you can reply here with.

HTH.

Cheers,


Brett

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Florian Fainelli]

On 12/9/25 23:29, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Fri, 12 Dec 2025 07:29:37 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.12-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on 
BMIPS_GENERIC:

Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
-- 
Florian

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Ron Economos]

On 12/9/25 23:29, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 12 Dec 2025 07:29:37 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.12-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Built and booted successfully on RISC-V RV64 (HiFive Unmatched).

Tested-by: Ron Economos <re@w6rz.net>

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Naresh Kamboju]

On Wed, 10 Dec 2025 at 13:03, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 12 Dec 2025 07:29:37 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
>         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.12-rc1.gz
> or in the git tree and branch at:
>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.

Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>

## Build
* kernel: 6.17.12-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit: e7c0ca6d291c41a8a9648a5016ce9b73e492aa3d
* git describe: v6.17.10-208-ge7c0ca6d291c
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.17.y/build/v6.17.10-208-ge7c0ca6d291c

## Test Regressions (compared to v6.17.10-147-gc434a9350a1d)

## Metric Regressions (compared to v6.17.10-147-gc434a9350a1d)

## Test Fixes (compared to v6.17.10-147-gc434a9350a1d)

## Metric Fixes (compared to v6.17.10-147-gc434a9350a1d)

## Test result summary
total: 116299, pass: 98676, fail: 3761, skip: 13862, xfail: 0

## Build Summary
* arc: 5 total, 5 passed, 0 failed
* arm: 139 total, 139 passed, 0 failed
* arm64: 57 total, 54 passed, 3 failed
* i386: 18 total, 18 passed, 0 failed
* mips: 34 total, 33 passed, 1 failed
* parisc: 4 total, 4 passed, 0 failed
* powerpc: 40 total, 39 passed, 1 failed
* riscv: 25 total, 25 passed, 0 failed
* s390: 22 total, 22 passed, 0 failed
* sh: 5 total, 5 passed, 0 failed
* sparc: 4 total, 3 passed, 1 failed
* x86_64: 49 total, 48 passed, 1 failed

## Test suites summary
* boot
* commands
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-efivarfs
* kselftest-exec
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-kcmp
* kselftest-kvm
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-mincore
* kselftest-mm
* kselftest-mqueue
* kselftest-net
* kselftest-net-mptcp
* kselftest-openat2
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-rust
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-tc-testing
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user_events
* kselftest-vDSO
* kselftest-x86
* kunit
* kvm-unit-tests
* lava
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-build-clang
* log-parser-build-gcc
* log-parser-test
* ltp-capability
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-hugetlb
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* perf
* rcutorture
* rt-tests-cyclicdeadline
* rt-tests-pi-stress
* rt-tests-pmqtest
* rt-tests-rt-migrate-test
* rt-tests-signaltest

--
Linaro LKFT
https://lkft.linaro.org

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 345 bytes --]

On Wed, Dec 10, 2025 at 04:29:30PM +0900, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.

Tested-by: Mark Brown <broonie@kernel.org>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Dileep malepu]

On Wed, Dec 10, 2025 at 1:05 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 12 Dec 2025 07:29:37 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
>         https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.12-rc1.gz
> or in the git tree and branch at:
>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Build and Boot Report for 6.17.12-rc1

The kernel version 6.17.12 was built and boot-tested using qemu-x86_64
and qemu-arm64 with the default configuration (defconfig). The build and boot
processes completed successfully, and the kernel operated as expected
in the virtualized environments without any issues.
No dmesg regressions found.

Build Details :
Builds : arm64, x86_64
Kernel Version: 6.17.12
Configuration : defconfig
Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Commit : e7c0ca6d291c41a8a9648a5016ce9b73e492aa3d

Tested-by: Dileep Malepu <dileep.debian@gmail.com>

Best regards,
Dileep Malepu

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Jeffrin Thalakkottoor]

On Thu, Dec 11, 2025 at 12:35 AM Brett A C Sheffield <bacs@librecast.net> wrote:
>
> On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> > On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
> > > >  compiled and booted 6.17.12-rc1+
> > > > Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> > > >
> > > > sudo dmesg -l errr  shows  error
> > > >
> > > > j$sudo dmesg -l err
> > > > [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> > > > $
> > >
> > > Is ths new?  if so, can you bisect?
> >
> > this is new related. Previous stable release err and warn disappeared
> > (i think i changed  .config)
> >
> > can you give me a  step by step tutorial  for git bisect
>
> 1) cd to wherever you have your kernel checked out
>
> 2) `git bisect start`
>
> 3) if you're already on a known-bad commit, then mark it as such:
>
>   `git bisect bad`
>
> 4) Mark the last known good commit as such:
>
>   `git bisect good <commit / tag>`
>
> git bisect will choose a commit to test.
>
> 5) Build, install and boot your kernel as you usually do
>
> 6) Run whatever test you need to determine if the booted kernel is good or bad
> (check dmesg in this case)
>
> 7) Mark the commit as good or bad. Git will choose another commit for you.
>
> 8) Goto 5.
>
> `git help bisect` will give you more information.
>
> At the end of the process git will tell you the first bad commit found.  You can
> dump the bisection log with:
>
> `git bisect log`
>
> which you can reply here with.
>
> HTH.
>
> Cheers,
>
>
> Brett
Thnaks for the tutorial  :)
1. should i start with the bad commit first ?
2. how to move forward or backward in commits ?
3. what is the point in re-compiling the kernel  if it cannot narrow
down and  test news lines of code







-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Brett A C Sheffield]

On 2025-12-11 21:09, Jeffrin Thalakkottoor wrote:
> On Thu, Dec 11, 2025 at 12:35 AM Brett A C Sheffield <bacs@librecast.net> wrote:
> >
> > On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> > > On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
> > > > >  compiled and booted 6.17.12-rc1+
> > > > > Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> > > > >
> > > > > sudo dmesg -l errr  shows  error
> > > > >
> > > > > j$sudo dmesg -l err
> > > > > [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> > > > > $
> > > >
> > > > Is ths new?  if so, can you bisect?
> > >
> > > this is new related. Previous stable release err and warn disappeared
> > > (i think i changed  .config)
> > >
> > > can you give me a  step by step tutorial  for git bisect
> >
> > 1) cd to wherever you have your kernel checked out
> >
> > 2) `git bisect start`
> >
> > 3) if you're already on a known-bad commit, then mark it as such:
> >
> >   `git bisect bad`
> >
> > 4) Mark the last known good commit as such:
> >
> >   `git bisect good <commit / tag>`
> >
> > git bisect will choose a commit to test.
> >
> > 5) Build, install and boot your kernel as you usually do
> >
> > 6) Run whatever test you need to determine if the booted kernel is good or bad
> > (check dmesg in this case)
> >
> > 7) Mark the commit as good or bad. Git will choose another commit for you.
> >
> > 8) Goto 5.
> >
> > `git help bisect` will give you more information.
> >
> > At the end of the process git will tell you the first bad commit found.  You can
> > dump the bisection log with:
> >
> > `git bisect log`
> >
> > which you can reply here with.
> >
> > HTH.
> >
> > Cheers,
> >
> >
> > Brett
> Thnaks for the tutorial  :)
> 1. should i start with the bad commit first ?

You start by marking one good (past) commit and one bad commit. It doesn't
matter what order.

You have at least one "bad" commit you know of: 4112049d7836ad4233321c3d2b6853db1627c49c

This is the 6.12.62-rc1 commit that you reported had the error.

So, in your kernel worktree:

`git bisect start`
`git bisect bad 4112049d7836ad4233321c3d2b6853db1627c49c`

Now we need to tell git bisect the most recent "good" commit we know of (where
the error didn't occur).

If you already know the commit or tag of a previous version where you did not get the
error, mark that as good. If not, pick a previous release, check it out, and go
to step 5.

> 2. how to move forward or backward in commits ?

git bisect will do that for you as soon as you mark a good and bad commit. If
you want to manually test a specific commit, just `git checkout <ref>` as usual, and
continue at step 5 in the instructions I gave you.

> 3. what is the point in re-compiling the kernel  if it cannot narrow
> down and  test news lines of code

We're narrowing down the error to a specific kernel commit. Once we know which
specific commit introduced the error, we can look at the lines changed and try
to understand why.  We need your help to find that commit, because it's
happening on your system.

Please do read `git help bisect` (man 1 git-bisect). It explains all this better
than I can.

Thanks for testing and good luck!


Brett

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Jeffrin Thalakkottoor]

On Thu, Dec 11, 2025 at 10:11 PM Brett A C Sheffield <bacs@librecast.net> wrote:
>
> On 2025-12-11 21:09, Jeffrin Thalakkottoor wrote:
> > On Thu, Dec 11, 2025 at 12:35 AM Brett A C Sheffield <bacs@librecast.net> wrote:
> > >
> > > On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> > > > On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> > > > <gregkh@linuxfoundation.org> wrote:
> > > > >
> > > > > On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
> > > > > >  compiled and booted 6.17.12-rc1+
> > > > > > Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> > > > > >
> > > > > > sudo dmesg -l errr  shows  error
> > > > > >
> > > > > > j$sudo dmesg -l err
> > > > > > [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> > > > > > $
> > > > >
> > > > > Is ths new?  if so, can you bisect?
> > > >
> > > > this is new related. Previous stable release err and warn disappeared
> > > > (i think i changed  .config)
> > > >
> > > > can you give me a  step by step tutorial  for git bisect
> > >
> > > 1) cd to wherever you have your kernel checked out
> > >
> > > 2) `git bisect start`
> > >
> > > 3) if you're already on a known-bad commit, then mark it as such:
> > >
> > >   `git bisect bad`
> > >
> > > 4) Mark the last known good commit as such:
> > >
> > >   `git bisect good <commit / tag>`
> > >
> > > git bisect will choose a commit to test.
> > >
> > > 5) Build, install and boot your kernel as you usually do
> > >
> > > 6) Run whatever test you need to determine if the booted kernel is good or bad
> > > (check dmesg in this case)
> > >
> > > 7) Mark the commit as good or bad. Git will choose another commit for you.
> > >
> > > 8) Goto 5.
> > >
> > > `git help bisect` will give you more information.
> > >
> > > At the end of the process git will tell you the first bad commit found.  You can
> > > dump the bisection log with:
> > >
> > > `git bisect log`
> > >
> > > which you can reply here with.
> > >
> > > HTH.
> > >
> > > Cheers,
> > >
> > >
> > > Brett
> > Thnaks for the tutorial  :)
> > 1. should i start with the bad commit first ?
>
> You start by marking one good (past) commit and one bad commit. It doesn't
> matter what order.
>
> You have at least one "bad" commit you know of: 4112049d7836ad4233321c3d2b6853db1627c49c
>
> This is the 6.12.62-rc1 commit that you reported had the error.
>
> So, in your kernel worktree:
>
> `git bisect start`
> `git bisect bad 4112049d7836ad4233321c3d2b6853db1627c49c`
>
> Now we need to tell git bisect the most recent "good" commit we know of (where
> the error didn't occur).
>
> If you already know the commit or tag of a previous version where you did not get the
> error, mark that as good. If not, pick a previous release, check it out, and go
> to step 5.
>
> > 2. how to move forward or backward in commits ?
>
> git bisect will do that for you as soon as you mark a good and bad commit. If
> you want to manually test a specific commit, just `git checkout <ref>` as usual, and
> continue at step 5 in the instructions I gave you.
>
> > 3. what is the point in re-compiling the kernel  if it cannot narrow
> > down and  test news lines of code
>
> We're narrowing down the error to a specific kernel commit. Once we know which
> specific commit introduced the error, we can look at the lines changed and try
> to understand why.  We need your help to find that commit, because it's
> happening on your system.
>
> Please do read `git help bisect` (man 1 git-bisect). It explains all this better
> than I can.
>
> Thanks for testing and good luck!
>
>
> Brett
>
Now i  have a much clearer vision. Thanks a  ton  !




-- 
software engineer
rajagiri school of engineering and technology

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Jeffrin Thalakkottoor]

On Thu, Dec 11, 2025 at 10:11 PM Brett A C Sheffield <bacs@librecast.net> wrote:
>
> On 2025-12-11 21:09, Jeffrin Thalakkottoor wrote:
> > On Thu, Dec 11, 2025 at 12:35 AM Brett A C Sheffield <bacs@librecast.net> wrote:
> > >
> > > On 2025-12-10 19:13, Jeffrin Thalakkottoor wrote:
> > > > On Wed, Dec 10, 2025 at 6:17 PM Greg Kroah-Hartman
> > > > <gregkh@linuxfoundation.org> wrote:
> > > > >
> > > > > On Wed, Dec 10, 2025 at 04:22:21PM +0530, Jeffrin Thalakkottoor wrote:
> > > > > >  compiled and booted 6.17.12-rc1+
> > > > > > Version: AMD A4-4000 APU with Radeon(tm) HD Graphics
> > > > > >
> > > > > > sudo dmesg -l errr  shows  error
> > > > > >
> > > > > > j$sudo dmesg -l err
> > > > > > [   39.915487] Error: Driver 'pcspkr' is already registered, aborting...
> > > > > > $
> > > > >
> > > > > Is ths new?  if so, can you bisect?
> > > >
> > > > this is new related. Previous stable release err and warn disappeared
> > > > (i think i changed  .config)
> > > >
> > > > can you give me a  step by step tutorial  for git bisect
> > >
> > > 1) cd to wherever you have your kernel checked out
> > >
> > > 2) `git bisect start`
> > >
> > > 3) if you're already on a known-bad commit, then mark it as such:
> > >
> > >   `git bisect bad`
> > >
> > > 4) Mark the last known good commit as such:
> > >
> > >   `git bisect good <commit / tag>`
> > >
> > > git bisect will choose a commit to test.
> > >
> > > 5) Build, install and boot your kernel as you usually do
> > >
> > > 6) Run whatever test you need to determine if the booted kernel is good or bad
> > > (check dmesg in this case)
> > >
> > > 7) Mark the commit as good or bad. Git will choose another commit for you.
> > >
> > > 8) Goto 5.
> > >
> > > `git help bisect` will give you more information.
> > >
> > > At the end of the process git will tell you the first bad commit found.  You can
> > > dump the bisection log with:
> > >
> > > `git bisect log`
> > >
> > > which you can reply here with.
> > >
> > > HTH.
> > >
> > > Cheers,
> > >
> > >
> > > Brett
> > Thnaks for the tutorial  :)
> > 1. should i start with the bad commit first ?
>
> You start by marking one good (past) commit and one bad commit. It doesn't
> matter what order.
>
> You have at least one "bad" commit you know of: 4112049d7836ad4233321c3d2b6853db1627c49c
>
> This is the 6.12.62-rc1 commit that you reported had the error.
>
> So, in your kernel worktree:
>
> `git bisect start`
> `git bisect bad 4112049d7836ad4233321c3d2b6853db1627c49c`
>
> Now we need to tell git bisect the most recent "good" commit we know of (where
> the error didn't occur).
>
> If you already know the commit or tag of a previous version where you did not get the
> error, mark that as good. If not, pick a previous release, check it out, and go
> to step 5.
>
> > 2. how to move forward or backward in commits ?
>
> git bisect will do that for you as soon as you mark a good and bad commit. If
> you want to manually test a specific commit, just `git checkout <ref>` as usual, and
> continue at step 5 in the instructions I gave you.
>
> > 3. what is the point in re-compiling the kernel  if it cannot narrow
> > down and  test news lines of code
>
> We're narrowing down the error to a specific kernel commit. Once we know which
> specific commit introduced the error, we can look at the lines changed and try
> to understand why.  We need your help to find that commit, because it's
> happening on your system.
>
> Please do read `git help bisect` (man 1 git-bisect). It explains all this better
> than I can.
>
> Thanks for testing and good luck!
>
>
> Brett
>

I do not see that error anymore. may be  i have made changes in configuration.
THANKS



--
software engineer
rajagiri school of engineering and technology

Re: [PATCH 6.17 00/60] 6.17.12-rc1 review

[Jon Hunter]

On Wed, 10 Dec 2025 16:29:30 +0900, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.17.12 release.
> There are 60 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Fri, 12 Dec 2025 07:29:37 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.17.12-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.17.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

All tests passing for Tegra ...

Test results for stable-v6.17:
    10 builds:	10 pass, 0 fail
    28 boots:	28 pass, 0 fail
    120 tests:	120 pass, 0 fail

Linux version:	6.17.12-rc1-ge7c0ca6d291c
Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
                tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000,
                tegra194-p3509-0000+p3668-0000, tegra20-ventana,
                tegra210-p2371-2180, tegra210-p3450-0000,
                tegra30-cardhu-a04

Tested-by: Jon Hunter <jonathanh@nvidia.com>

Jon