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
| ||
|
Message-ID: <20220228011626.GA169657@roeck-us.net> Date: Sun, 27 Feb 2022 17:16:26 -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-rc6 On Sun, Feb 27, 2022 at 03:00:26PM -0800, Linus Torvalds wrote: > Nobody can claim that last week was *normal*, but whatever crazy > things are going on in the world (and I personally had "Zombie > apocalypse" on my bingo card, not "Putin has a mental breakdown"), it > doesn't seem to have affected the kernel much. > > Things continue to look normal both in commit numbers and in > diffstats. We have the usual bulk being drivers (networking, gpu, iio, > clk, and usb stand out, but there's a smattering of other stuff), with > the rest being mixed. The only thing that stands out as a bit unusual > is some further btrfs defrag fixes. But even they stand out not so > much because they are enormous, as just because they are bigger than > most of the rest, which is pretty small. > > Other notable areas: core networking, tracing, and selftests. As > usual, details are in the appended shortlog. > > While things look reasonably normal, we _are_ getting pretty late in > the release, and we still have a number of known regressions. They > don't seem all that big and scary, but some of them were reported > right after the rc1 release, so they are getting a bit long in the > tooth. I'd hate to have to delay 5.17 just because of them, and I'm > starting to be a bit worried here. I think all the affected > maintainers know who they are... > > So if you are a subsystem maintainer, and you have one of those > regressions on your list, please go make them a priority. And if you > don't know what I'm talking about, please do look up the reports by > regzbot and Guenter Roeck. I added links below to make it really easy. > > But on the whole things look fine. Just a few remaining warts is all. > But the more testing to verify, the better. > > Linus > > https://lore.kernel.org/all/164598944963.346832.10219407090470852309@leemhuis.info/ > https://lore.kernel.org/all/20220221024743.GA4097766@roeck-us.net/ > Build results: total: 155 pass: 153 fail: 2 Failed builds: powerpc:skiroot_defconfig sparc64:allmodconfig 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/ Fixed with commit 5a72345e6a78 ("powerpc: Fix STACKTRACE=n build") in linux-next. --- 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/ and in linux-next as commit 3c5412cdec9f ("pinctrl-sunxi: sunxi_pinctrl_gpio_direction_in/output: use correct offset"). The fix exposes a lockdep splat for which a fix is posted at https://lore.kernel.org/lkml/20220216040037.22730-1-samuel@sholland.org/ --- Building sparc64:allmodconfig ... failed -------------- Error log: <stdin>:1517:2: warning: #warning syscall clone3 not implemented [-Wcpp] sparc64-linux-ld: drivers/memory/omap-gpmc.o: in function `gpmc_probe_generic_child': omap-gpmc.c:(.text.unlikely+0x14c4): undefined reference to `of_platform_device_create' Introduced by commit 4cd335dae3cf ("mtd: rawnand: omap2: Prevent invalid configuration and build error"). Reported: https://lore.kernel.org/lkml/20220219150836.GA1035394@roeck-us.net/T/#t Fix: https://patchwork.ozlabs.org/project/linux-mtd/patch/20220219193600.24892-1-rogerq@kernel.org/ Guenter
Powered by blists - more mailing lists