From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: madhuparnabhowmik10@gmail.com, mingo@redhat.com,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, ebiederm@xmission.com,
christian.brauner@ubuntu.com, oleg@redhat.com,
joel@joelfernandes.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
frextrite@gmail.com, rcu@vger.kernel.org
Subject: Re: [PATCH] sched.h: Annotate sighand_struct with __rcu
Date: Fri, 24 Jan 2020 09:58:52 +0530 [thread overview]
Message-ID: <20200124042852.GC23699@madhuparna-HP-Notebook> (raw)
In-Reply-To: <20200123164108.GQ2935@paulmck-ThinkPad-P72>
On Thu, Jan 23, 2020 at 08:41:08AM -0800, Paul E. McKenney wrote:
> On Thu, Jan 23, 2020 at 08:23:05PM +0530, madhuparnabhowmik10@gmail.com wrote:
> > From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> >
> > This patch fixes the following sparse errors by annotating the
> > sighand_struct with __rcu
> >
> > kernel/fork.c:1511:9: error: incompatible types in comparison expression
> > kernel/exit.c:100:19: error: incompatible types in comparison expression
> > kernel/signal.c:1370:27: error: incompatible types in comparison expression
> >
> > This fix introduces the following sparse error in signal.c due to
> > checking the sighand pointer without rcu primitives:
> >
> > kernel/signal.c:1386:21: error: incompatible types in comparison expression
> >
> > This new sparse error is also addressed in this patch.
> >
> > Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> > ---
> > include/linux/sched.h | 2 +-
> > kernel/signal.c | 3 ++-
> > 2 files changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/linux/sched.h b/include/linux/sched.h
> > index b511e178a89f..7a351360ad54 100644
> > --- a/include/linux/sched.h
> > +++ b/include/linux/sched.h
> > @@ -918,7 +918,7 @@ struct task_struct {
> >
> > /* Signal handlers: */
> > struct signal_struct *signal;
> > - struct sighand_struct *sighand;
> > + struct sighand_struct __rcu *sighand;
> > sigset_t blocked;
> > sigset_t real_blocked;
> > /* Restored if set_restore_sigmask() was used: */
> > diff --git a/kernel/signal.c b/kernel/signal.c
> > index bcd46f547db3..1272def37462 100644
> > --- a/kernel/signal.c
> > +++ b/kernel/signal.c
> > @@ -1383,7 +1383,8 @@ struct sighand_struct *__lock_task_sighand(struct task_struct *tsk,
> > * must see ->sighand == NULL.
> > */
> > spin_lock_irqsave(&sighand->siglock, *flags);
> > - if (likely(sighand == tsk->sighand))
> > + if (likely(sighand == rcu_dereference_protected(tsk->sighand,
> > + lockdep_is_held(&sighand->siglock))))
>
> Given that the return value is never dereferenced, you can use
> rcu_access_pointer(), which may be used outside of an RCU read-side
> critical section, and thus does not need the lockdep_is_held(). So this
> change would save a line of code and would be a bit easier on the eyes.
>
Okay got it! I will send the updated patch soon.
Thank you,
Madhuparna
> Thanx, Paul
>
> > break;
> > spin_unlock_irqrestore(&sighand->siglock, *flags);
> > }
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2020-01-24 4:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 14:53 [PATCH] sched.h: Annotate sighand_struct with __rcu madhuparnabhowmik10
2020-01-23 16:41 ` Paul E. McKenney
2020-01-24 4:28 ` Madhuparna Bhowmik [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-24 4:59 madhuparnabhowmik10
2020-01-25 21:41 ` Christian Brauner
2020-01-26 1:23 ` Paul E. McKenney
2020-01-27 9:29 ` Oleg Nesterov
2020-01-27 12:23 ` Christian Brauner
2020-01-27 17:14 ` Madhuparna Bhowmik
2020-01-22 18:11 madhuparnabhowmik10
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=20200124042852.GC23699@madhuparna-HP-Notebook \
--to=madhuparnabhowmik10@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=ebiederm@xmission.com \
--cc=frextrite@gmail.com \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=vincent.guittot@linaro.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