This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y and the diffstat can be found below.
thanks,
greg k-h
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 6.1.1-rc1
Ferry Toth ftoth@exalondelft.nl usb: ulpi: defer ulpi_register on ulpi_read_id timeout
Nikolaus Voss nikolaus.voss@haag-streit.com KEYS: encrypted: fix key instantiation with user-provided data
Paulo Alcantara pc@cjr.nz cifs: fix oops during encryption
Shruthi Sanil shruthi.sanil@intel.com usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake
Heikki Krogerus heikki.krogerus@linux.intel.com usb: typec: ucsi: Resume in separate work
Tony Nguyen anthony.l.nguyen@intel.com igb: Initialize mailbox message for VF reset
Martin Kaiser martin@kaiser.cx staging: r8188eu: fix led register settings
Reka Norman rekanorman@chromium.org xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N
Andy Chi andy.chi@canonical.com ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
Johan Hovold johan@kernel.org USB: serial: f81534: fix division by zero on line-speed change
Johan Hovold johan@kernel.org USB: serial: f81232: fix division by zero on line-speed change
Bruno Thomsen bruno.thomsen@gmail.com USB: serial: cp210x: add Kamstrup RF sniffer PIDs
Duke Xin duke_xinanwen@163.com USB: serial: option: add Quectel EM05-G modem
Szymon Heidrich szymon.heidrich@gmail.com usb: gadget: uvc: Prevent buffer overflow in setup handler
Jan Kara jack@suse.cz udf: Fix extending file within last block
Jan Kara jack@suse.cz udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size
Jan Kara jack@suse.cz udf: Fix preallocation discarding at indirect extent boundary
Jan Kara jack@suse.cz udf: Discard preallocation before extending file with a hole
Sean Anderson sean.anderson@seco.com irqchip/ls-extirq: Fix endianness detection
John Thomson git@johnthomson.fastmail.com.au mips: ralink: mt7621: do not use kzalloc too early
John Thomson git@johnthomson.fastmail.com.au mips: ralink: mt7621: soc queries and tests as functions
John Thomson git@johnthomson.fastmail.com.au mips: ralink: mt7621: define MT7621_SYSC_BASE with __iomem
John Thomson git@johnthomson.fastmail.com.au PCI: mt7621: Add sentinel to quirks table
David Michael fedora.dm0@gmail.com libbpf: Fix uninitialized warning in btf_dump_dump_type_data
Nathan Chancellor nathan@kernel.org x86/vdso: Conditionally export __vdso_sgx_enter_enclave()
-------------
Diffstat:
Documentation/security/keys/trusted-encrypted.rst | 3 +- Makefile | 4 +- arch/mips/include/asm/mach-ralink/mt7621.h | 4 +- arch/mips/ralink/mt7621.c | 97 ++++++++++----- arch/x86/entry/vdso/vdso.lds.S | 2 + drivers/irqchip/irq-ls-extirq.c | 2 +- drivers/net/ethernet/intel/igb/igb_main.c | 2 +- drivers/pci/controller/pcie-mt7621.c | 3 +- drivers/staging/r8188eu/core/rtw_led.c | 25 +--- drivers/usb/common/ulpi.c | 2 +- drivers/usb/dwc3/dwc3-pci.c | 2 +- drivers/usb/gadget/function/f_uvc.c | 5 +- drivers/usb/host/xhci-pci.c | 4 +- drivers/usb/serial/cp210x.c | 2 + drivers/usb/serial/f81232.c | 12 +- drivers/usb/serial/f81534.c | 12 +- drivers/usb/serial/option.c | 3 + drivers/usb/typec/ucsi/ucsi.c | 17 ++- drivers/usb/typec/ucsi/ucsi.h | 1 + fs/cifs/cifsglob.h | 68 ++++++++++ fs/cifs/cifsproto.h | 4 +- fs/cifs/misc.c | 4 +- fs/cifs/smb2ops.c | 143 ++++++++++------------ fs/udf/inode.c | 76 +++++------- fs/udf/truncate.c | 48 +++----- security/keys/encrypted-keys/encrypted.c | 6 +- sound/pci/hda/patch_realtek.c | 2 + tools/lib/bpf/btf_dump.c | 2 +- 28 files changed, 319 insertions(+), 236 deletions(-)
On 12/19/22 12:22, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y and the diffstat can be found below.
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan skhan@linuxfoundation.org
thanks, -- Shuah
On 12/19/22 11:22, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.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 f.fainelli@gmail.com
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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.
Successfully cross-compiled for arm64 (bcm2711_defconfig, GCC 10.2.0) and powerpc (ps3_defconfig, GCC 12.2.0).
Tested-by: Bagas Sanjaya bagasdotme@gmail.com
On 12/19/22 11:22 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.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
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
Hi Greg,
6.1.1-rc1 tested.
Run tested on: - Intel Alder Lake x86_64 (nuc12 i7-1260P) - SolidRun Cubox-i Dual/Quad - NXP iMX6 (Cubox-i4Pro)
In addition - build tested for: - Allwinner A64 - Allwinner H3 - Allwinner H5 - Allwinner H6 - NXP iMX8 - Qualcomm Dragonboard - Rockchip RK3288 - Rockchip RK3328 - Rockchip RK3399pro - Samsung Exynos
Tested-by: Rudi Heitbaum rudi@heitbaum.com -- Rudi
On Tue, 20 Dec 2022 at 00:53, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.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.1.1-rc1 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-6.1.y * git commit: 4478ff938eb5814bd2ae93b7e2d68c4fe54e9380 * git describe: v6.1-26-g4478ff938eb5 * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1-26...
## Test Regressions (compared to v6.1)
## Metric Regressions (compared to v6.1)
## Test Fixes (compared to v6.1)
## Metric Fixes (compared to v6.1)
## Test result summary total: 173959, pass: 152611, fail: 5743, skip: 15605, xfail: 0
## Build Summary * arc: 5 total, 5 passed, 0 failed * arm: 151 total, 146 passed, 5 failed * arm64: 49 total, 48 passed, 1 failed * i386: 39 total, 36 passed, 3 failed * mips: 30 total, 28 passed, 2 failed * parisc: 8 total, 8 passed, 0 failed * powerpc: 38 total, 32 passed, 6 failed * riscv: 16 total, 16 passed, 0 failed * s390: 16 total, 16 passed, 0 failed * sh: 14 total, 12 passed, 2 failed * sparc: 8 total, 8 passed, 0 failed * x86_64: 42 total, 41 passed, 1 failed
## Test suites summary * boot * fwts * igt-gpu-tools * kselftest-android * kselftest-arm64 * kselftest-arm64/arm64.btitest.bti_c_func * kselftest-arm64/arm64.btitest.bti_j_func * kselftest-arm64/arm64.btitest.bti_jc_func * kselftest-arm64/arm64.btitest.bti_none_func * kselftest-arm64/arm64.btitest.nohint_func * kselftest-arm64/arm64.btitest.paciasp_func * kselftest-arm64/arm64.nobtitest.bti_c_func * kselftest-arm64/arm64.nobtitest.bti_j_func * kselftest-arm64/arm64.nobtitest.bti_jc_func * kselftest-arm64/arm64.nobtitest.bti_none_func * kselftest-arm64/arm64.nobtitest.nohint_func * kselftest-arm64/arm64.nobtitest.paciasp_func * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-drivers-dma-buf * kselftest-efivarfs * kselftest-filesystems * kselftest-filesystems-binderfs * kselftest-firmware * kselftest-fpu * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * kselftest-livepatch * kselftest-membarrier * kselftest-memfd * kselftest-memory-hotplug * kselftest-mincore * kselftest-mount * kselftest-mqueue * kselftest-net-forwarding * kselftest-net-mptcp * kselftest-netfilter * kselftest-nsfs * kselftest-openat2 * kselftest-pid_namespace * kselftest-pidfd * kselftest-proc * kselftest-pstore * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-tc-testing * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-vm * kselftest-x86 * kselftest-zram * kunit * kvm-unit-tests * libgpiod * libhugetlbfs * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-open-posix-tests * ltp-pty * ltp-sched * ltp-securebits * ltp-smoke * ltp-syscalls * ltp-tracing * network-basic-tests * packetdrill * perf * perf/Zstd-perf.data-compression * rcutorture * v4l2-compliance * vdso
-- Linaro LKFT https://lkft.linaro.org
Hi Greg,
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
Build test (gcc version 12.2.1 20221127): mips: 52 configs -> no failure arm: 100 configs -> no failure arm64: 3 configs -> no failure x86_64: 4 configs -> no failure alpha allmodconfig -> no failure csky allmodconfig -> no failure powerpc allmodconfig -> no failure riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> no failure
Boot test: x86_64: Booted on my test laptop. No regression. x86_64: Booted on qemu. No regression. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. Regression.
Note: networking.service is failing on mips ci20 boards. Issue seen on v6.1 also. Will report upstream after bisecting.
[1]. https://openqa.qa.codethink.co.uk/tests/2420 [2]. https://openqa.qa.codethink.co.uk/tests/2427
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
Hi Greg,
On Tue, 20 Dec 2022 at 12:26, Sudip Mukherjee (Codethink) sudipm.mukherjee@gmail.com wrote:
Hi Greg,
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
<snip>
Boot test: x86_64: Booted on my test laptop. No regression. x86_64: Booted on qemu. No regression. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. Regression.
Note: networking.service is failing on mips ci20 boards. Issue seen on v6.1 also. Will report upstream after bisecting.
This has already been fixed in mainline by: ca637c0ece14 ("MIPS: DTS: CI20: fix reset line polarity of the ethernet controller")
I have tested 6.1.1-rc1 with the above commit cherry-picked and it has fixed the issue.
On Tue, Dec 20, 2022 at 02:31:20PM +0000, Sudip Mukherjee wrote:
Hi Greg,
On Tue, 20 Dec 2022 at 12:26, Sudip Mukherjee (Codethink) sudipm.mukherjee@gmail.com wrote:
Hi Greg,
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
<snip>
Boot test: x86_64: Booted on my test laptop. No regression. x86_64: Booted on qemu. No regression. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. Regression.
Note: networking.service is failing on mips ci20 boards. Issue seen on v6.1 also. Will report upstream after bisecting.
This has already been fixed in mainline by: ca637c0ece14 ("MIPS: DTS: CI20: fix reset line polarity of the ethernet controller")
I have tested 6.1.1-rc1 with the above commit cherry-picked and it has fixed the issue.
Thanks for letting me know, now queued up.
greg k-h
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 500 pass: 498 fail: 2 Failed tests: arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:net,default:zynq-zc702:rootfs arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:zynq-zed:rootfs
The failure bisects to commit e013ba1e4e12 ("usb: ulpi: defer ulpi_register on ulpi_read_id timeout") and is inherited from mainline. Reverting the offending patch fixes the problem.
Guenter
--- # bad: [4478ff938eb5814bd2ae93b7e2d68c4fe54e9380] Linux 6.1.1-rc1 # good: [830b3c68c1fb1e9176028d02ef86f3cf76aa2476] Linux 6.1 git bisect start 'HEAD' 'v6.1' # good: [38b8e682acfa37b80cb947cecc743431c72a6c1d] USB: serial: option: add Quectel EM05-G modem git bisect good 38b8e682acfa37b80cb947cecc743431c72a6c1d # good: [8baa56d13f1bef9c621bc967c66b789022e9614e] staging: r8188eu: fix led register settings git bisect good 8baa56d13f1bef9c621bc967c66b789022e9614e # good: [aaac7e5db89b4f46c871b9a5c188bfbe6ae21b83] usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake git bisect good aaac7e5db89b4f46c871b9a5c188bfbe6ae21b83 # good: [acbd8d17388466ea19eb52c2239c2e9d34906381] KEYS: encrypted: fix key instantiation with user-provided data git bisect good acbd8d17388466ea19eb52c2239c2e9d34906381 # bad: [e013ba1e4e12b523bff42f600d598ff65a69c27b] usb: ulpi: defer ulpi_register on ulpi_read_id timeout git bisect bad e013ba1e4e12b523bff42f600d598ff65a69c27b # first bad commit: [e013ba1e4e12b523bff42f600d598ff65a69c27b] usb: ulpi: defer ulpi_register on ulpi_read_id timeout
On Tue, Dec 20, 2022 at 07:00:49AM -0800, Guenter Roeck wrote:
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 500 pass: 498 fail: 2 Failed tests: arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:net,default:zynq-zc702:rootfs arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:zynq-zed:rootfs
The failure bisects to commit e013ba1e4e12 ("usb: ulpi: defer ulpi_register on ulpi_read_id timeout") and is inherited from mainline. Reverting the offending patch fixes the problem.
Odd, yet that same commit works just fine on 6.0 and 5.15 and 5.10? I hadn't had any reports of this being an issue on Linus's tree either, did I miss those?
thanks,
greg k-h
On Tue, Dec 20, 2022 at 04:10:55PM +0100, Greg Kroah-Hartman wrote:
On Tue, Dec 20, 2022 at 07:00:49AM -0800, Guenter Roeck wrote:
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 500 pass: 498 fail: 2 Failed tests: arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:net,default:zynq-zc702:rootfs arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:zynq-zed:rootfs
The failure bisects to commit e013ba1e4e12 ("usb: ulpi: defer ulpi_register on ulpi_read_id timeout") and is inherited from mainline. Reverting the offending patch fixes the problem.
Odd, yet that same commit works just fine on 6.0 and 5.15 and 5.10? I hadn't had any reports of this being an issue on Linus's tree either, did I miss those?
I testbed has a bad hair day. The reports for the other branches are wrong. I restarted the tests and expect them to fail there as well. Sorry for that.
You probably didn't see any reports on mainline because I didn't report the issue there yet. There are so many failures in mainline that it is a bit difficult to keep up. This would be a full-time job, and I just don't have that much time, sorry.
Guenter
On 20. 12. 22, 17:11, Guenter Roeck wrote:
You probably didn't see any reports on mainline because I didn't report the issue there yet. There are so many failures in mainline that it is a bit difficult to keep up.
Just heads up, these are breakages in 6.1 known to me:
an io_uring 32bit test crashes the kernel: https://lore.kernel.org/all/c80c1e3f-800b-dc49-f2f5-acc8ceb34d51@gmail.com/
Fixed in io_uring tree.
bind() of previously bound port no longer fails: https://lore.kernel.org/all/6b971a4e-c7d8-411e-1f92-fda29b5b2fb9@kernel.org/
No fix available and revert close to impossible.
And most important, mremap() is broken in 6.1, so mostly everything fails in some random way: https://lore.kernel.org/all/20221216163227.24648-1-vbabka@suse.cz/T/#u
Fixed in -mm.
maybe it can help...
On Wed, Dec 21, 2022 at 07:34:04AM +0100, Jiri Slaby wrote:
On 20. 12. 22, 17:11, Guenter Roeck wrote:
You probably didn't see any reports on mainline because I didn't report the issue there yet. There are so many failures in mainline that it is a bit difficult to keep up.
Just heads up, these are breakages in 6.1 known to me:
an io_uring 32bit test crashes the kernel: https://lore.kernel.org/all/c80c1e3f-800b-dc49-f2f5-acc8ceb34d51@gmail.com/
Fixed in io_uring tree.
bind() of previously bound port no longer fails: https://lore.kernel.org/all/6b971a4e-c7d8-411e-1f92-fda29b5b2fb9@kernel.org/
No fix available and revert close to impossible.
And most important, mremap() is broken in 6.1, so mostly everything fails in some random way: https://lore.kernel.org/all/20221216163227.24648-1-vbabka@suse.cz/T/#u
Fixed in -mm.
maybe it can help...
Thanks for the list, I'll keep an eye out for these...
greg k-h
On 21.12.22 07:34, Jiri Slaby wrote:
On 20. 12. 22, 17:11, Guenter Roeck wrote:
You probably didn't see any reports on mainline because I didn't report the issue there yet. There are so many failures in mainline that it is a bit difficult to keep up.
Just heads up, these are breakages in 6.1 known to me:
an io_uring 32bit test crashes the kernel: https://lore.kernel.org/all/c80c1e3f-800b-dc49-f2f5-acc8ceb34d51@gmail.com/
Fixed in io_uring tree.
Just BTW: afaics the fix is now in mainline as 990a4de57e44
bind() of previously bound port no longer fails: https://lore.kernel.org/all/6b971a4e-c7d8-411e-1f92-fda29b5b2fb9@kernel.org/
No fix available and revert close to impossible.
Also just BTW: fix posted yesterday.
And most important, mremap() is broken in 6.1, so mostly everything fails in some random way: https://lore.kernel.org/all/20221216163227.24648-1-vbabka@suse.cz/T/#u
Fixed in -mm.
That one seems to fix an annoying issue many people might run into (at least it looks like it to my untrained eyes), which is the reason why I write this mail.
Andrew moved that fix from mm-hotfixes-unstable to mm-hotfixes-stable yesterday and I assume he'll send it to Linus pretty soon now to ensure it makes it into -rc1, so that the stable team can pick it up. It might be a bad season to ask this, but that made me wonder:
Should that patch have progressed quicker? And if so: how to make that happen when a similar situation arises in the future? Should somebody (the developer of the patch? me?) kindly ask the maintainer in question to sent the fix straight to Linus once it spend 1 or 2 days in next?
It's not the first time that I see something like this, that's why I'm wondering if I should do something in such situations.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
On Tue, Dec 20, 2022 at 08:11:35AM -0800, Guenter Roeck wrote:
On Tue, Dec 20, 2022 at 04:10:55PM +0100, Greg Kroah-Hartman wrote:
On Tue, Dec 20, 2022 at 07:00:49AM -0800, Guenter Roeck wrote:
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
Build results: total: 155 pass: 155 fail: 0 Qemu test results: total: 500 pass: 498 fail: 2 Failed tests: arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:net,default:zynq-zc702:rootfs arm:xilinx-zynq-a9:multi_v7_defconfig:usb0:mem128:zynq-zed:rootfs
The failure bisects to commit e013ba1e4e12 ("usb: ulpi: defer ulpi_register on ulpi_read_id timeout") and is inherited from mainline. Reverting the offending patch fixes the problem.
Odd, yet that same commit works just fine on 6.0 and 5.15 and 5.10? I hadn't had any reports of this being an issue on Linus's tree either, did I miss those?
I testbed has a bad hair day. The reports for the other branches are wrong. I restarted the tests and expect them to fail there as well. Sorry for that.
No worries, I've deleted this patch from all branches now, thanks.
greg k-h
On Mon, 19 Dec 2022 20:22:39 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y and the diffstat can be found below.
thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v6.1: 11 builds: 11 pass, 0 fail 28 boots: 28 pass, 0 fail 130 tests: 130 pass, 0 fail
Linux version: 6.1.1-rc1-g4478ff938eb5 Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, 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
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y and the diffstat can be found below.
thanks,
greg k-h
Compiled and booted on my x86_64 and ARM64 test systems. No errors or regressions.
Tested-by: Allen Pais apais@linux.microsoft.com
Thanks.
On Mon, Dec 19, 2022 at 2:23 PM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +0000. Anything received after that time might be too late.
Hi, Compiled and tested on my x86_64 test systems, no errors or regressions to report.
Tested-by: Slade Watkins srw@sladewatkins.net
Yours, -- Slade
On Mon, Dec 19, 2022 at 08:22:39PM +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y and the diffstat can be found below.
thanks,
greg k-h
Tested rc1 against the Fedora build system (aarch64, armv7, ppc64le, s390x, x86_64), and boot tested x86_64. No regressions noted.
Tested-by: Justin M. Forbes jforbes@fedoraproject.org
On Mon, 19 Dec 2022 20:22:39 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.1 release. There are 25 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 Wed, 21 Dec 2022 18:29:31 +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.1.1-rc1.g... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y and the diffstat can be found below.
thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v6.1: 11 builds: 11 pass, 0 fail 28 boots: 28 pass, 0 fail 130 tests: 130 pass, 0 fail
Linux version: 6.1.1-rc1-g4478ff938eb5 Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Tested-by: Thierry Reding treding@nvidia.com
-
Allen Pais -
Bagas Sanjaya -
Florian Fainelli -
Greg Kroah-Hartman -
Guenter Roeck -
Jiri Slaby -
Jon Hunter -
Justin Forbes -
Naresh Kamboju -
Ron Economos -
Rudi Heitbaum -
Shuah Khan -
Slade Watkins -
Sudip Mukherjee -
Sudip Mukherjee (Codethink)
-
Thierry Reding -
Thorsten Leemhuis