[CCing a few people]
On 24.05.24 12:31, Ilkka Naulapää wrote:
I have encountered a critical bug in the Linux vanilla kernel that leads to a kernel panic during the shutdown or reboot process. The issue arises after all services, including `journald`, have been stopped. As a result, the machine fails to complete the shutdown or reboot procedure, effectively causing the system to hang and not shut down or reboot.
Thx for the report. Not my area of expertise, so take this with a gain of salt. But given the versions your mention in your report and the screenshot that mentioned tracefs_free_inode I suspect this is caused by baa23a8d4360d ("tracefs: Reset permissions on remount if permissions are options"). A few fixes for it will soon hit mainline and are meant to be backported to affected stable trees:
https://lore.kernel.org/all/20240523212406.254317554@goodmis.org/ https://lore.kernel.org/all/20240523174419.1e5885a5@gandalf.local.home/
You might want to try them – or recheck once they hit the stable trees you are about. If they don't work, please report back.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.
Here are the details of the issue:
- Affected Versions: Before kernel version 6.8.10, the bug caused a
quick display of a kernel trace dump before the shutdown/reboot completed. Starting from version 6.8.10 and continuing into version 6.9.0 and 6.9.1, this issue has escalated to a kernel panic, preventing the shutdown or reboot from completing and leaving the machine stuck.
- Symptoms:
- In normal shutdown/reboot scenarios, the kernel trace dump briefly
appears as the last message on the screen.
- In rescue mode, the kernel panic message is displayed. Normally it
is not shown.
Since `journald` is stopped before this issue occurs, no textual logs are available. However, I have captured two pictures illustrating these related issues, which I am attaching to this email for your reference. Also added my custom kernel config.
Thank you for your attention to this matter. Please let me know if any additional information is required to assist in diagnosing and resolving this bug.
Best regards,
Ilkka Naulapää