linux-kernel - Re: 2.6.36-git11 -- kernel/pid.c:419 invoked rcu_dereference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101107184711.GB15561@linux.vnet.ibm.com>
Date:	Sun, 7 Nov 2010 10:47:11 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Miles Lane <miles.lane@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.36-git11 -- kernel/pid.c:419 invoked
 rcu_dereference_check() without protection!

On Fri, Oct 29, 2010 at 01:22:28AM -0400, Miles Lane wrote:
> [ INFO: suspicious rcu_dereference_check() usage. ]
> ---------------------------------------------------
> kernel/pid.c:419 invoked rcu_dereference_check() without protection!
> 
> other info that might help us debug this:
> 
> 
> rcu_scheduler_active = 1, debug_locks = 1
> 1 lock held by ureadahead/943:
>  #0:  (tasklist_lock){.+.+..}, at: [<ffffffff810ec497>]
> sys_ioprio_set+0x8e/0x2aa
> 
> stack backtrace:
> Pid: 943, comm: ureadahead Not tainted 2.6.36-git11 #8
> Call Trace:
>  [<ffffffff8105d335>] lockdep_rcu_dereference+0x9d/0xa5
>  [<ffffffff8104c825>] find_task_by_pid_ns+0x3f/0x58
>  [<ffffffff8104c85b>] find_task_by_vpid+0x1d/0x1f
>  [<ffffffff810ec4c6>] sys_ioprio_set+0xbd/0x2aa
>  [<ffffffff813547a3>] ? trace_hardirqs_on_thunk+0x3a/0x3f
>  [<ffffffff81002aab>] system_call_fastpath+0x16/0x1b

Could you please try the patch from Sergey Senozhatsky, currently
in -mm, that may be found at http://lkml.org/lkml/2010/10/29/168?

							Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/