Control: reassign -1 src:linux Control: severity -1 grave On Sun, 19 May 2024 15:25:06 +0200 Salvatore Bonaccorso <car...@debian.org> wrote: > Control: reassign -1 src:systemd > > On Sat, May 18, 2024 at 10:25:14PM +0200, Matteo Settenvini wrote: > > Package: src:linux > > Version: 6.8.9-1 > > Severity: important > > Tags: upstream > > > > Dear Maintainer, > > > > booting kernel 6.8.9-1 with dracut, systemd, and btrfs as the root device fails > > to mount the root partition. I just tried the kernel from sid and it seems indeed \ > > affected. The 6.7 kernel from trixie is instead booting fine even after > > regenerating all initrds. > > > > According to bl...@debian.org, this is likely due to > > https://github.com/torvalds/linux/commit/a1912f712188291f9d7d434fba155461f1ebef66 > > > > See https://lwn.net/Articles/973997/ > > The deprecation was there for a while indeed and dropped by upstream > for 6.8-rc1. But it looks systemd is adressing this with > > https://github.com/systemd/systemd/commit/e3828d7103a99a15a1e947ba3063294ead590631 > > As we wont apply a local Debian patch unless upstream Linux decides to > facilitate this by adding a noop option back, then I think it's best > to reassign this bug to systemd and close it once the above change is > applied.
Sorry, but I am reassigning back and bumping severity to stop migration, as this is a kernel regression, as a stable userspace interface was removed, which breaks booting existing systems. Hence I am quite sure the new kernel should not move to testing for the time being. We might (or might not, still to be seen, given detecting mount options that a kernel support is an absolute mess and it risks breaking booting with the LTS kernels) put in a workaround in userspace in a while, but this really should be reverted in the kernel. If mount options are no longer required, they should simply remain as no-ops. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
