public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Ilkka Naulapää" <digirigawa@gmail.com>
Cc: "Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	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: Wed, 29 May 2024 14:47:57 -0400	[thread overview]
Message-ID: <20240529144757.79d09eeb@rorschach.local.home> (raw)
In-Reply-To: <CAE4VaRE3_MYVt+=BGs+WVCmKUiQv0VSKE2NT+JmUPKG0UF+Juw@mail.gmail.com>

On Wed, 29 May 2024 21:36:08 +0300
Ilkka Naulapää <digirigawa@gmail.com> wrote:

> applied your patch without others, so trace and panic there.
> Screenshot attached. Also tested kernels backward and found out that

Bah, it's still in an RCU callback, which doesn't tell us why a
normal inode is being sent to the trace inode free list.

> this trace bug first triggered on 6.6-rc1.

Hmm, that's when eventfs was added.

> 
> Let me know if you need more assistance with this.

Let me make a debug patch (that crashes on this issue) for that kernel,
and perhaps you could bisect it?

Thanks!

-- Steve

  reply	other threads:[~2024-05-29 18:48 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
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 [this message]
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=20240529144757.79d09eeb@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