From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: suspicious RCU usage warning on tracing/urgent
Date: Mon, 11 Sep 2023 17:09:29 -0400 [thread overview]
Message-ID: <20230911170929.1b0ede14@gandalf.local.home> (raw)
In-Reply-To: <20230911120053.ca82f545e7f46ea753deda18@kernel.org>
On Mon, 11 Sep 2023 12:00:53 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> But it seems correctly taking srcu_read_lock().
>
> 452
> 453 ei = ti->private;
> 454 idx = srcu_read_lock(&eventfs_srcu);
> 455 list_for_each_entry_rcu(ef, &ei->e_top_files, list) {
> 456 create_dentry(ef, dentry, false);
> 457 }
> 458 srcu_read_unlock(&eventfs_srcu, idx);
> 459 return dcache_dir_open(inode, file);
> 460 }
> 461
>
> This may false-positive warning, or srcu_read_lock() is not enough for
> list_for_each_entry_rcu(). In latter case, maybe we need to use a
> mutex instead of srcu for update the ef.
Oops, that should be list_for_each_entry_srcu().
Thanks!
>
> BTW, the ftracetest itself passed without any problem.
Thanks for testing as well!
-- Steve
prev parent reply other threads:[~2023-09-12 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 3:00 suspicious RCU usage warning on tracing/urgent Masami Hiramatsu
2023-09-11 21:09 ` 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=20230911170929.1b0ede14@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=paulmck@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).