[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211028094351.617b7c2ea7c56055ee68d909@kernel.org>
Date: Thu, 28 Oct 2021 09:43:51 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Kalesh Singh <kaleshsingh@...gle.com>,
Masami Hiramatsu <mhiramat@...nel.org>, surenb@...gle.com,
hridya@...gle.com, namhyung@...nel.org, kernel-team@...roid.com,
Ingo Molnar <mingo@...hat.com>, Shuah Khan <shuah@...nel.org>,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [PATCH 2/3] tracing/kselftests: Remove triggers with references
before their definitions
On Wed, 27 Oct 2021 19:54:54 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 27 Oct 2021 16:26:00 -0700
> Kalesh Singh <kaleshsingh@...gle.com> wrote:
>
> > > Why don't you use 'tac'? I love that idea :)
> > > Did you find any issue?
> >
> > Hi Masami,
> >
> > Thanks for the reviews. As with the first set of patches using tac
> > gives a regression here, though I'm not sure why it doesn't work -- I
> > also thought reversing the order would handle any dependencies
> > correctly.
>
> Right, because are triggers not added by list_add_rcu() which adds to
> the head of the list.
Oops, so are the triggers shown in the reverse order?
(newer entry is top, older one is bottom)
Then do we need this patch, because we don't care about the
dependency.
> If anything, shouldn't things be removed in order?
Hmm, I think the trigger itself might better to be changed. If any dependency in
the trigger list, it can not be restored from the copied file, like
below may fail.
cat events/foo/bar/trigger > /tmp/foo.bar.trigger
cat /tmp/foo.bar.trigger > events/foo/bar/trigger
(of course we can use 'tac' to restore it ...)
This is
Thank you,
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists