linux-kernel - Re: Linux 5.17-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 6 Feb 2022 16:11:41 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.17-rc3

On Sun, Feb 06, 2022 at 12:40:28PM -0800, Linus Torvalds wrote:
> Things look fairly normal so far, with a pretty average number of
> commits for an rc3 release.
> 
> The diffstat shows that we've had more filesystem activity than is
> perhaps usual, The filesystem activity is all over, ranging from cifs
> re-introducing fscache support after the rewrite, to vfs-level error
> handling fixes, to just regular filesystem-specific fixes (btrfs,
> ext4, xfs), to some unicode Kconfig cleanups. So it's not one single
> thing, it just happened that we had more filesystem stuff than is
> perhaps common at this point.
> 
> That said, driver fixes (networking, gpu, sound, pin control, platform
> drivers,scsi etc) still dominate. On the driver side, some reverts to
> re-enable hw-accelerated scrolling for legacy fbdev devices perhaps
> stand out.
> 
> Outside of that, it's a mixed bag of random stuff - the usual arch
> updates (kvm noise stands out), generic networking and core kernel,
> and tooling (selftests and perf). And some documentation fixes.
> 
> Shortlog appended for more details, but I don't see anything that
> makes me worried for the 5.17 release. Knock wood.
> 
> Please go test,
> 

Build results:
	total: 155 pass: 154 fail: 1
Failed builds:
	powerpc:skiroot_defconfig
Qemu test results:
	total: 488 pass: 487 fail: 1
Failed tests:
	arm:orangepi-pc:multi_v7_defconfig:usb1:net,nic:sun8i-h3-orangepi-pc:rootfs

---

Building powerpc:skiroot_defconfig ... failed
--------------
arch/powerpc/kernel/stacktrace.c: In function 'handle_backtrace_ipi':
arch/powerpc/kernel/stacktrace.c:171:9: error: implicit declaration of function 'nmi_cpu_backtrace'

Introduced with commit 1614b2b11fab29 ("arch: Make ARCH_STACKWALK
independent of STACKTRACE"). Discussed at
https://lore.kernel.org/lkml/YeE2VWwHO50gFw9M@hirez.programming.kicks-ass.net/T/
No fix posted as far as I know, and no recent progress.

---
Building arm:orangepi-pc:multi_v7_defconfig:usb1:net,nic:sun8i-h3-orangepi-pc:rootfs ... running ........R.... failed (no root file system)

Introduced with 8df89a7cbc63 ("pinctrl-sunxi: don't call
pinctrl_gpio_direction()"). Fix posted at
https://patchwork.kernel.org/project/linux-media/patch/0f536cd8-01db-5d16-2cec-ec6d19409a49@xs4all.nl/

---

Unrelated to testing with my testbed, the following problem was found
while merging stable releases into Chrome OS.

Upstream commit 9de2b9286a6d ("ASoC: mediatek: Check for error clk pointer")
introduces a regression affecting all (or at least many many) Mediatek
systems using the mtk-scpsys driver. Revert and explanation posted at
https://lore.kernel.org/lkml/20220205014755.699603-1-linux@roeck-us.net/.

Guenter