From: peterz@infradead.org
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: rostedt@goodmis.org, mingo@redhat.com, mhiramat@kernel.org,
mbenes@suse.cz, linux-kernel@vger.kernel.org,
Paul McKenney <paulmck@kernel.org>
Subject: Re: [PATCH] ftrace: Fix missing synchronize_rcu() removing trampoline from kallsyms
Date: Fri, 11 Sep 2020 13:41:32 +0200 [thread overview]
Message-ID: <20200911114132.GH1362448@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200901091617.31837-1-adrian.hunter@intel.com>
On Tue, Sep 01, 2020 at 12:16:17PM +0300, Adrian Hunter wrote:
> Add synchronize_rcu() after list_del_rcu() in
> ftrace_remove_trampoline_from_kallsyms() to protect readers of
> ftrace_ops_trampoline_list (in ftrace_get_trampoline_kallsym)
> which is used when kallsyms is read.
>
> Fixes: fc0ea795f53c8d ("ftrace: Add symbols for ftrace trampolines")
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> kernel/trace/ftrace.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index 275441254bb5..4e64367c9774 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -2782,6 +2782,7 @@ static void ftrace_remove_trampoline_from_kallsyms(struct ftrace_ops *ops)
> {
> lockdep_assert_held(&ftrace_lock);
> list_del_rcu(&ops->list);
> + synchronize_rcu();
> }
Hurmph, we've just done a ton of that:
ftrace_shutdown()
synchronize_rcu_tasks_rude()
ftrace_trampoline_free()
ftrace_remove_trampoline_from_kallsyms()
So would it not be better to move that call before the existing
synchronize_rcu_tasks stuff rather than adding another synchronize_rcu()
call?
next prev parent reply other threads:[~2020-09-11 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 9:16 Adrian Hunter
2020-09-11 11:41 ` peterz [this message]
2020-09-11 12:55 ` Adrian Hunter
2020-09-11 13:26 ` peterz
2020-09-18 16:23 ` Steven Rostedt
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=20200911114132.GH1362448@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®