From: Christian Brauner <christian.brauner@ubuntu.com>
To: madhuparnabhowmik10@gmail.com, mingo@redhat.com,
peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, ebiederm@xmission.com,
oleg@redhat.com, paulmck@kernel.org
Cc: joel@joelfernandes.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
frextrite@gmail.com, rcu@vger.kernel.org,
Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
Subject: Re: [PATCH] sched.h: Annotate sighand_struct with __rcu
Date: Sat, 25 Jan 2020 22:41:06 +0100 [thread overview]
Message-ID: <37A3FF92-0958-46DD-AFB1-CE72000B153F@ubuntu.com> (raw)
In-Reply-To: <20200124045908.26389-1-madhuparnabhowmik10@gmail.com>
On January 24, 2020 5:59:08 AM GMT+01:00, 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 fixed in this patch.
>
>Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
>---
> include/linux/sched.h | 2 +-
> kernel/signal.c | 2 +-
> 2 files changed, 2 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..9ad8dea93dbb 100644
>--- a/kernel/signal.c
>+++ b/kernel/signal.c
>@@ -1383,7 +1383,7 @@ 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_access_pointer(tsk->sighand)))
> break;
> spin_unlock_irqrestore(&sighand->siglock, *flags);
> }
If Paul is happy with this and nobody wants to take it I'll pick this up.
Thanks!
Christian
next prev parent reply other threads:[~2020-01-25 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 4:59 madhuparnabhowmik10
2020-01-25 21:41 ` Christian Brauner [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 14:53 madhuparnabhowmik10
2020-01-23 16:41 ` Paul E. McKenney
2020-01-24 4:28 ` 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=37A3FF92-0958-46DD-AFB1-CE72000B153F@ubuntu.com \
--to=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=madhuparnabhowmik10@gmail.com \
--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
all inboxes | Powered by JetHome®