From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Martin KaFai Lau <kafai@fb.com>,
linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: ftrace module init race/bug
Date: Mon, 7 Nov 2016 15:50:46 -0500 [thread overview]
Message-ID: <20161107155046.59df2467@gandalf.local.home> (raw)
In-Reply-To: <20161107203540.GA29563@ast-mbp.thefacebook.com>
On Mon, 7 Nov 2016 12:35:42 -0800
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> > Actually, this may be correct. I need to audit the other
> > do_for_each_ftrace_rec() loops.
>
> yep, the __ftrace_hash_rec_update() has !FTRACE_FL_DISABLED check,
> so I thought ftrace_shutdown() may need it too.
> Should I send the above patch with proper sob?
Yeah, go ahead.
-- Steve
prev parent reply other threads:[~2016-11-07 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 19:46 ftrace module init race/bug Alexei Starovoitov
2016-11-07 20:08 ` Steven Rostedt
2016-11-07 20:35 ` Alexei Starovoitov
2016-11-07 20:50 ` Steven Rostedt [this message]
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=20161107155046.59df2467@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).