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: Tue, 28 May 2024 14:47:43 -0400	[thread overview]
Message-ID: <20240528144743.149e351b@rorschach.local.home> (raw)
In-Reply-To: <CAE4VaRHaijpV1CC9Jo_Lg4tNQb_+=LTHwygOp5Bm2z5ErVzeow@mail.gmail.com>

On Tue, 28 May 2024 07:51:30 +0300
Ilkka Naulapää <digirigawa@gmail.com> wrote:

> yeah, the cache_from_obj tracing bug (without panic) has been
> displayed quite some time now - maybe even since 6.7.x or so. I could
> try checking a few versions back for this and try bisecting it if I
> can find when this started.
> 

OK, so I don't think the commit your last bisect hit is the cause of
the bug. It added a delay (via RCU) and is causing the real bug to blow
up more.

Can you add this patch to v6.9.2 and hopefully it crashes in a better
location that we can find where the mixup happened.

You may need to add the other commit (too if this doesn't trigger.

Thanks,

-- Steve

diff --git a/fs/tracefs/inode.c b/fs/tracefs/inode.c
index 417c840e6403..7af3f696696d 100644
--- a/fs/tracefs/inode.c
+++ b/fs/tracefs/inode.c
@@ -50,6 +50,7 @@ static struct inode *tracefs_alloc_inode(struct super_block *sb)
 	list_add_rcu(&ti->list, &tracefs_inodes);
 	spin_unlock_irqrestore(&tracefs_inode_lock, flags);
 
+	ti->magic = 20240823;
 	return &ti->vfs_inode;
 }
 
@@ -66,6 +67,7 @@ static void tracefs_free_inode(struct inode *inode)
 	struct tracefs_inode *ti = get_tracefs(inode);
 	unsigned long flags;
 
+	BUG_ON(ti->magic != 20240823);
 	spin_lock_irqsave(&tracefs_inode_lock, flags);
 	list_del_rcu(&ti->list);
 	spin_unlock_irqrestore(&tracefs_inode_lock, flags);
@@ -271,16 +273,6 @@ static const struct inode_operations tracefs_file_inode_operations = {
 	.setattr	= tracefs_setattr,
 };
 
-struct inode *tracefs_get_inode(struct super_block *sb)
-{
-	struct inode *inode = new_inode(sb);
-	if (inode) {
-		inode->i_ino = get_next_ino();
-		simple_inode_init_ts(inode);
-	}
-	return inode;
-}
-
 struct tracefs_mount_opts {
 	kuid_t uid;
 	kgid_t gid;
@@ -448,6 +440,17 @@ static const struct super_operations tracefs_super_operations = {
 	.show_options	= tracefs_show_options,
 };
 
+struct inode *tracefs_get_inode(struct super_block *sb)
+{
+	struct inode *inode = new_inode(sb);
+	BUG_ON(sb->s_op != &tracefs_super_operations);
+	if (inode) {
+		inode->i_ino = get_next_ino();
+		simple_inode_init_ts(inode);
+	}
+	return inode;
+}
+
 /*
  * It would be cleaner if eventfs had its own dentry ops.
  *
diff --git a/fs/tracefs/internal.h b/fs/tracefs/internal.h
index f704d8348357..dda7d2708e30 100644
--- a/fs/tracefs/internal.h
+++ b/fs/tracefs/internal.h
@@ -16,6 +16,7 @@ struct tracefs_inode {
 	};
 	/* The below gets initialized with memset_after(ti, 0, vfs_inode) */
 	struct list_head	list;
+	unsigned long		magic;
 	unsigned long           flags;
 	void                    *private;
 };

  reply	other threads:[~2024-05-28 18:47 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 [this message]
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=20240528144743.149e351b@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