From: Steven Rostedt <rostedt@goodmis.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Ilkka Naulapää" <digirigawa@gmail.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: Bug in Kernel 6.8.x, 6.9.x Causing Trace/Panic During Shutdown/Reboot
Date: Mon, 27 May 2024 18:31:39 -0400 [thread overview]
Message-ID: <20240527183139.42b6123c@rorschach.local.home> (raw)
In-Reply-To: <5b79732b-087c-411f-a477-9b837566673e@leemhuis.info>
On Fri, 24 May 2024 12:50:08 +0200
"Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.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.
You state "Before kernel version 6.8.10, the bug caused ...". Does that
mean that a bug was happening before v6.8.10? But did not cause a panic?
I just noticed your second screen shot from your report, and it has:
"cache_from_obj: Wrong slab cache, tracefs_inode_cache but object is from inode_cache"
So somehow an tracefs_inode was allocated from the inode_cache and is
now being freed by the tracefs_inode logic? Did this happen before
6.8.10? If so, this code could just be triggering an issue from an
unrelated bug.
Thanks,
-- Steve
next prev parent reply other threads:[~2024-05-27 22:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 10:31 Bug in Kernel 6.8.x, 6.9.x Causing Trace/Panic During Shutdown/Reboot Ilkka Naulapää
2024-05-24 10:50 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-24 17:14 ` Steven Rostedt
2024-05-24 17:20 ` Steven Rostedt
2024-05-26 17:42 ` Ilkka Naulapää
2024-05-27 16:40 ` Ilkka Naulapää
2024-05-27 18:14 ` Greg KH
2024-05-27 21:44 ` Steven Rostedt
2024-05-28 4:08 ` Ilkka Naulapää
2024-05-27 22:31 ` Steven Rostedt [this message]
2024-05-28 4:51 ` Ilkka Naulapää
2024-05-28 18:47 ` Steven Rostedt
2024-05-29 18:36 ` Ilkka Naulapää
2024-05-29 18:47 ` Steven Rostedt
2024-05-29 19:48 ` Steven Rostedt
2024-05-30 13:02 ` Ilkka Naulapää
2024-05-30 13:59 ` Steven Rostedt
2024-06-02 7:32 ` Ilkka Naulapää
2024-06-12 13:36 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-12 15:56 ` Steven Rostedt
2024-06-13 7:32 ` Ilkka Naulapää
2024-06-13 7:48 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-18 14:52 ` Steven Rostedt
2024-06-19 10:41 ` Ilkka Naulapää
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240527183139.42b6123c@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=digirigawa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox