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 15:48:24 -0400	[thread overview]
Message-ID: <20240529154824.2db8133a@rorschach.local.home> (raw)
In-Reply-To: <20240529144757.79d09eeb@rorschach.local.home>

On Wed, 29 May 2024 14:47:57 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

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

Can you try this on 6.6-rc1 and see if it gives you any other splats?

Hmm, you can switch it to WARN_ON and that way it may not crash the
machine, and you can use dmesg to get the output.

Thanks,

-- Steve


diff --git a/fs/tracefs/inode.c b/fs/tracefs/inode.c
index de5b72216b1a..a090495e78c9 100644
--- a/fs/tracefs/inode.c
+++ b/fs/tracefs/inode.c
@@ -39,13 +39,17 @@ static struct inode *tracefs_alloc_inode(struct super_block *sb)
 		return NULL;
 
 	ti->flags = 0;
+	ti->magic = 20240823;
 
 	return &ti->vfs_inode;
 }
 
 static void tracefs_free_inode(struct inode *inode)
 {
-	kmem_cache_free(tracefs_inode_cachep, get_tracefs(inode));
+	struct tracefs_inode *ti = get_tracefs(inode);
+
+	BUG_ON(ti->magic != 20240823);
+	kmem_cache_free(tracefs_inode_cachep, ti);
 }
 
 static ssize_t default_read_file(struct file *file, char __user *buf,
@@ -147,16 +151,6 @@ static const struct inode_operations tracefs_dir_inode_operations = {
 	.rmdir		= tracefs_syscall_rmdir,
 };
 
-struct inode *tracefs_get_inode(struct super_block *sb)
-{
-	struct inode *inode = new_inode(sb);
-	if (inode) {
-		inode->i_ino = get_next_ino();
-		inode->i_atime = inode->i_mtime = inode_set_ctime_current(inode);
-	}
-	return inode;
-}
-
 struct tracefs_mount_opts {
 	kuid_t uid;
 	kgid_t gid;
@@ -384,6 +378,7 @@ static void tracefs_dentry_iput(struct dentry *dentry, struct inode *inode)
 		return;
 
 	ti = get_tracefs(inode);
+	BUG_ON(ti->magic != 20240823);
 	if (ti && ti->flags & TRACEFS_EVENT_INODE)
 		eventfs_set_ef_status_free(dentry);
 	iput(inode);
@@ -568,6 +563,18 @@ struct dentry *eventfs_end_creating(struct dentry *dentry)
 	return dentry;
 }
 
+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();
+		inode->i_atime = inode->i_mtime = inode_set_ctime_current(inode);
+	}
+	return inode;
+}
+
 /**
  * tracefs_create_file - create a file in the tracefs filesystem
  * @name: a pointer to a string containing the name of the file to create.
diff --git a/fs/tracefs/internal.h b/fs/tracefs/internal.h
index 69c2b1d87c46..9f6f303a9e58 100644
--- a/fs/tracefs/internal.h
+++ b/fs/tracefs/internal.h
@@ -9,6 +9,7 @@ enum {
 struct tracefs_inode {
 	unsigned long           flags;
 	void                    *private;
+	unsigned long		magic;
 	struct inode            vfs_inode;
 };
 

  reply	other threads:[~2024-05-29 19: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
2024-05-29 19:48             ` Steven Rostedt [this message]
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=20240529154824.2db8133a@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