From: Tom Rix <trix@redhat.com>
To: paulmck@kernel.org
Cc: dave@stgolabs.net, josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
joel@joelfernandes.org, natechancellor@gmail.com,
ndesaulniers@google.com, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org, clang-built-linux@googlegroups.com
Subject: Re: [PATCH] rcutorture: remove unneeded check
Date: Fri, 9 Oct 2020 14:18:41 -0700 [thread overview]
Message-ID: <03e3eeed-6072-ccb8-a9c6-c79a99c701b8@redhat.com> (raw)
In-Reply-To: <20201009201825.GL29330@paulmck-ThinkPad-P72>
On 10/9/20 1:18 PM, Paul E. McKenney wrote:
> On Fri, Oct 09, 2020 at 12:47:36PM -0700, trix@redhat.com wrote:
>> From: Tom Rix <trix@redhat.com>
>>
>> clang static analysis reports this problem:
>>
>> rcutorture.c:1999:2: warning: Called function pointer
>> is null (null dereference)
>> cur_ops->sync(); /* Later readers see above write. */
>> ^~~~~~~~~~~~~~~
>>
>> This is a false positive triggered by an earlier, later ignored
>> NULL check of sync() op. By inspection of the rcu_torture_ops,
>> the sync() op is never uninitialized. So this earlier check is
>> not needed.
> You lost me on this one. This check is at the very beginning of
> rcu_torture_fwd_prog_nr(). Or are you saying that clang is seeing an
> earlier check in one of rcu_torture_fwd_prog_nr()'s callers? If so,
> where exactly is this check?
>
> In any case, the check is needed because all three functions are invoked
> if there is a self-propagating RCU callback that ensures that there is
> always an RCU grace period outstanding.
>
> Ah. Is clang doing local analysis and assuming that because there was
> a NULL check earlier, then the pointer might be NULL later? That does
> not seem to me to be a sound check.
>
> So please let me know exactly what is causing clang to emit this
> diagnostic. It might or might not be worth fixing this, but either way
> I need to understand the situation so as to be able to understand the
> set of feasible fixes.
>
> Thanx, Paul
In rcu_prog_nr() there is check for for sync.
if ( ... cur_op->sync ...
do something
This flags in clang's static analyzer as 'could be null'
later in the function, in a reachable block it is used
cur_ops->sync()
I agree this is not a good check that's why i said is was a false positive.
However when looking closer at how cur_ops is set, it is never uninitialized.
So the check is not needed.
This is not a fix, the code works fine. It is a small optimization.
Tom
>
>> Signed-off-by: Tom Rix <trix@redhat.com>
>> ---
>> kernel/rcu/rcutorture.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
>> index beba9e7963c8..6efc03a1d623 100644
>> --- a/kernel/rcu/rcutorture.c
>> +++ b/kernel/rcu/rcutorture.c
>> @@ -1989,7 +1989,7 @@ static void rcu_torture_fwd_prog_nr(struct rcu_fwd *rfp,
>> unsigned long stopat;
>> static DEFINE_TORTURE_RANDOM(trs);
>>
>> - if (cur_ops->call && cur_ops->sync && cur_ops->cb_barrier) {
>> + if (cur_ops->call && cur_ops->cb_barrier) {
>> init_rcu_head_on_stack(&fcs.rh);
>> selfpropcb = true;
>> }
>> --
>> 2.18.1
>>
next prev parent reply other threads:[~2020-10-09 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 19:47 trix
2020-10-09 20:18 ` Paul E. McKenney
2020-10-09 21:18 ` Tom Rix [this message]
2020-10-09 23:50 ` Paul E. McKenney
2020-10-10 0:24 ` Tom Rix
2020-10-10 2:57 ` Paul E. McKenney
2020-10-10 4:47 ` Tom Rix
2020-10-10 17:57 ` Paul E. McKenney
2020-10-10 18:07 ` Tom Rix
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=03e3eeed-6072-ccb8-a9c6-c79a99c701b8@redhat.com \
--to=trix@redhat.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dave@stgolabs.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.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®