From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: beaub@linux.microsoft.com, mark.rutland@arm.com,
mhiramat@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tracing: Have trace_event_file have ref counters" failed to apply to 5.4-stable tree
Date: Wed, 15 Nov 2023 12:36:53 -0500 [thread overview]
Message-ID: <2023111541-various-pliable-2a2d@gregkh> (raw)
In-Reply-To: <20231115123334.725cb742@rorschach.local.home>
On Wed, Nov 15, 2023 at 12:33:34PM -0500, Steven Rostedt wrote:
> On Wed, 15 Nov 2023 07:04:42 -0500
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > On Wed, Nov 15, 2023 at 06:58:14AM -0500, Greg KH wrote:
> > > On Mon, Nov 06, 2023 at 02:48:32PM -0500, Steven Rostedt wrote:
> > > >
> > > > [ This should work for v5.4 ]
> > > >
> > > > From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> > > > Subject: [PATCH] tracing: Have trace_event_file have ref counters
> > > >
> > > > commit bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 upstream
> > >
> > > All now queued up, thanks.
> >
> > No, wait, all of these break the build with this error:
> >
> > kernel/trace/trace_events.c: In function ‘remove_event_file_dir’:
> > kernel/trace/trace_events.c:1015:24: error: unused variable ‘child’ [-Werror=unused-variable]
> > 1015 | struct dentry *child;
> > | ^~~~~
> >
> > So I'm going to drop them now :(
> >
>
> Ah, this patch I didn't run through all my tests, like I did with the
> 6.6 patches, so I didn't test with fail on warnings. The patch deleted
> the following code:
>
> static void remove_event_file_dir(struct trace_event_file *file)
> {
> struct dentry *dir = file->dir;
> struct dentry *child;
>
> - if (dir) {
> - spin_lock(&dir->d_lock); /* probably unneeded */
> - list_for_each_entry(child, &dir->d_subdirs, d_child) {
> - if (d_really_is_positive(child)) /* probably unneeded */
> - d_inode(child)->i_private = NULL;
> - }
> - spin_unlock(&dir->d_lock);
> -
> + if (dir)
> tracefs_remove_recursive(dir);
> - }
>
> list_del(&file->list);
>
> The extra check that that utilized that child variable is no longer
> needed, and I forgot to delete the declaration of the child variable.
>
> Did you just want to delete that, or do you want me to create a new
> patch?
I need all new patches, sorry, these are long gone from my queue.
greg k-h
next prev parent reply other threads:[~2023-11-15 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 11:40 FAILED: patch "[PATCH] tracing: Have trace_event_file have ref counters" failed to apply to 5.4-stable tree gregkh
2023-11-06 19:48 ` Steven Rostedt
2023-11-15 11:58 ` Greg KH
2023-11-15 12:04 ` Greg KH
2023-11-15 17:33 ` Steven Rostedt
2023-11-15 17:36 ` Greg KH [this message]
2023-11-16 16:24 ` [v2] " Steven Rostedt
2023-11-24 16:06 ` Greg KH
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=2023111541-various-pliable-2a2d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=beaub@linux.microsoft.com \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--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