linux-kernel - Re: Bug in Kernel 6.8.x, 6.9.x Causing Trace/Panic During Shutdown/Reboot

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAE4VaRF80OhnaiqeP9STfLa5pORB31YSorgoJ92fQ8tsRovxqQ@mail.gmail.com>
Date: Sun, 26 May 2024 20:42:42 +0300
From: Ilkka Naulapää <digirigawa@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: "Linux regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info>, 
	Linux regressions mailing list <regressions@...ts.linux.dev>, stable@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: Bug in Kernel 6.8.x, 6.9.x Causing Trace/Panic During Shutdown/Reboot

hi,

I took 6.9.2 and applied that 0bcfd9aa4dafa to it. Now the kernel is
serving me both problems; the trace and the panic as the pic shows.

> To understand this, did you do anything with tracing? Before shutting down,
> is there anything in /sys/kernel/tracing/instances directory?
> Were any of the files/directories permissions in /sys/kernel/tracing changed?

And to answer your question, I did not do any tracing or so and the
/sys/kernel/tracing is empty.
Just plain boot-up, no matter if in full desktop or in bare rescue
mode, ends up the same way.

--Ilkka

On Fri, May 24, 2024 at 8:19 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Fri, 24 May 2024 12:50:08 +0200
> "Linux regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info> wrote:
>
> > > - 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.
>
> Ah, I bet it was this commit: baa23a8d4360d ("tracefs: Reset permissions on
> remount if permissions are options"), which added a "iput" callback to the
> dentry without calling iput, leaving stale inodes around.
>
> This is fixed with:
>
>   0bcfd9aa4dafa ("tracefs: Clear EVENT_INODE flag in tracefs_drop_inode()")
>
> Try adding just that patch. It will at least make it go back to what was
> happening before 6.8.10 (I hope!).
>
> -- Steve

Download attachment "6.9.2_trace_panic.heic" of type "image/heif" (2576274 bytes)