From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
To: Amol Grover <frextrite@gmail.com>
Cc: madhuparnabhowmik10@gmail.com, ebiederm@xmission.com,
oleg@redhat.com, christian.brauner@ubuntu.com, guro@fb.com,
tj@kernel.org, linux-kernel@vger.kernel.org, paulmck@kernel.org,
joel@joelfernandes.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] signal.c: Fix sparse warnings
Date: Wed, 5 Feb 2020 22:39:21 +0530 [thread overview]
Message-ID: <20200205170921.GA2755@madhuparna-HP-Notebook> (raw)
In-Reply-To: <20200205165138.GB22537@workstation-portable>
On Wed, Feb 05, 2020 at 10:21:38PM +0530, Amol Grover wrote:
> On Wed, Feb 05, 2020 at 09:53:19PM +0530, madhuparnabhowmik10@gmail.com wrote:
> > From: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> >
> > This patch fixes the following two sparse warnings caused due to
> > accessing RCU protected pointer tsk->parent without rcu primitives.
> >
> > kernel/signal.c:1948:65: warning: incorrect type in argument 1 (different address spaces)
> > kernel/signal.c:1948:65: expected struct task_struct *tsk
> > kernel/signal.c:1948:65: got struct task_struct [noderef] <asn:4> *parent
> > kernel/signal.c:1949:40: warning: incorrect type in argument 1 (different address spaces)
> > kernel/signal.c:1949:40: expected void const volatile *p
> > kernel/signal.c:1949:40: got struct cred const [noderef] <asn:4> *[noderef] <asn:4> *
> > kernel/signal.c:1949:40: warning: incorrect type in argument 1 (different address spaces)
> > kernel/signal.c:1949:40: expected void const volatile *p
> > kernel/signal.c:1949:40: got struct cred const [noderef] <asn:4> *[noderef] <asn:4> *
> >
> > Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>
> > ---
> > kernel/signal.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/signal.c b/kernel/signal.c
> > index 9ad8dea93dbb..3d59e5652d94 100644
> > --- a/kernel/signal.c
> > +++ b/kernel/signal.c
> > @@ -1945,8 +1945,8 @@ bool do_notify_parent(struct task_struct *tsk, int sig)
> > * correct to rely on this
> > */
> > rcu_read_lock();
> > - info.si_pid = task_pid_nr_ns(tsk, task_active_pid_ns(tsk->parent));
> > - info.si_uid = from_kuid_munged(task_cred_xxx(tsk->parent, user_ns),
> > + info.si_pid = task_pid_nr_ns(tsk, task_active_pid_ns(rcu_access_pointer(tsk->parent)));
> > + info.si_uid = from_kuid_munged(task_cred_xxx(rcu_access_pointer(tsk->parent), user_ns),
>
> Shouldn't rcu_dereference() OR rcu_dereference_check() be better suited
> here? Since, rcu_access_pointer() omits all lockdep checks.
>
I used rcu_access_pointer() because I thought the pointer is not
dereferenced. But it is dereferenced in task_pid() and task_cred_xxx().
Thank you for pointing out, I will send the updated patch.
Thanks,
Madhuparna
> Thanks
> Amol
>
> > task_uid(tsk));
> > rcu_read_unlock();
> >
> > --
> > 2.17.1
> >
next prev parent reply other threads:[~2020-02-05 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 16:23 madhuparnabhowmik10
2020-02-05 16:51 ` Amol Grover
2020-02-05 17:09 ` Madhuparna Bhowmik [this message]
2020-02-05 17:24 madhuparnabhowmik10
2020-02-05 22:59 ` Eric W. Biederman
2020-02-06 11:00 ` Madhuparna Bhowmik
2020-02-06 20:25 ` Joel Fernandes
2020-02-07 15:04 ` Madhuparna Bhowmik
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=20200205170921.GA2755@madhuparna-HP-Notebook \
--to=madhuparnabhowmik10@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=ebiederm@xmission.com \
--cc=frextrite@gmail.com \
--cc=guro@fb.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=tj@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
all inboxes | Powered by JetHome®