public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
	josh@joshtriplett.org, dvhltc@us.ibm.com, niv@us.ibm.com,
	tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
	Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
	eric.dumazet@gmail.com, jmorris@namei.org,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH RFC] pid: make setpgid() system call use RCU read-side critical section
Date: Mon, 30 Aug 2010 21:51:07 +0200	[thread overview]
Message-ID: <4C7C0BAB.3000709@suse.cz> (raw)
In-Reply-To: <20100830172631.GA11868@linux.vnet.ibm.com>

Ccing Oleg.

On 08/30/2010 07:26 PM, Paul E. McKenney wrote:
> [   23.584720] ===================================================
> [   23.585059] [ INFO: suspicious rcu_dereference_check() usage. ]
> [   23.585176] ---------------------------------------------------
> [   23.585176] kernel/pid.c:419 invoked rcu_dereference_check() without protection!
> [   23.585176]
> [   23.585176] other info that might help us debug this:
> [   23.585176]
> [   23.585176]
> [   23.585176] rcu_scheduler_active = 1, debug_locks = 1
> [   23.585176] 1 lock held by rc.sysinit/728:
> [   23.585176]  #0:  (tasklist_lock){.+.+..}, at: [<ffffffff8104771f>] sys_setpgid+0x5f/0x193
> [   23.585176]
> [   23.585176] stack backtrace:
> [   23.585176] Pid: 728, comm: rc.sysinit Not tainted 2.6.36-rc2 #2
> [   23.585176] Call Trace:
> [   23.585176]  [<ffffffff8105b436>] lockdep_rcu_dereference+0x99/0xa2
> [   23.585176]  [<ffffffff8104c324>] find_task_by_pid_ns+0x50/0x6a
> [   23.585176]  [<ffffffff8104c35b>] find_task_by_vpid+0x1d/0x1f
> [   23.585176]  [<ffffffff81047727>] sys_setpgid+0x67/0x193
> [   23.585176]  [<ffffffff810029eb>] system_call_fastpath+0x16/0x1b
> [   24.959669] type=1400 audit(1282938522.956:4): avc:  denied  { module_request } for  pid=766 comm="hwclock" kmod="char-major-10-135" scontext=system_u:system_r:hwclock_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclas
> 
> It turns out that the setpgid() system call fails to enter an RCU
> read-side critical section before doing a PID-to-task_struct translation.
> This commit therefore does rcu_read_lock() before the translation, and
> also does rcu_read_unlock() after the last use of the returned pointer.
> 
> Located-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
> 
>  sys.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/kernel/sys.c b/kernel/sys.c
> index e9ad444..05a4b0c 100644
> --- a/kernel/sys.c
> +++ b/kernel/sys.c
> @@ -938,6 +938,7 @@ SYSCALL_DEFINE2(setpgid, pid_t, pid, pid_t, pgid)
>  	write_lock_irq(&tasklist_lock);
>  
>  	err = -ESRCH;
> +	rcu_read_lock();
>  	p = find_task_by_vpid(pid);

AFAICT the missing lock doesn't harm due to the write_lock of tasklist
above. But is probably a good thing to do anyway.

regards,
-- 
js
suse labs

  reply	other threads:[~2010-08-30 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 17:26 [PATCH RFC] pid: make setpgid() system call use RCU read-side critical section Paul E. McKenney
2010-08-30 19:51 ` Jiri Slaby [this message]
2010-08-30 20:32   ` Paul E. McKenney
2010-09-09 22:15   ` Oleg Nesterov
2010-09-16  9:18     ` Jiri Slaby
2010-09-16 16:39       ` Oleg Nesterov
2010-08-31 13:02 ` David Howells
2010-08-31 15:12   ` Paul E. McKenney
2010-08-31 15:31     ` David Howells

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=4C7C0BAB.3000709@suse.cz \
    --to=jslaby@suse.cz \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jmorris@namei.org \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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