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
| ||
|
Date: Thu, 25 Oct 2012 00:41:47 -0700
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Oleg Nesterov <oleg@...hat.com>, Dave Jones <davej@...hat.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Serge Hallyn <serge.hallyn@...onical.com>,
linux-kernel@...r.kernel.org
Subject: Re: lots of suspicious RCU traces
On (10/25/12 09:06), Frederic Weisbecker wrote:
> >> > My understanding is (I may be wrong) that we can schedule() from ptrace chain to
> >> > some arbitrary task, which will continue its execution from the point where RCU assumes
> >> > CPU as not idle, while CPU in fact still in idle state -- no one said rcu_idle_exit()
> >> > (or similar) prior to schedule() call.
> >>
> >> Yeah but when we are in syscall_trace_leave(), the CPU shouldn't be in
> >> RCU idle mode. That's where the bug is. How do you manage to trigger
> >> this bug?
> >>
> >
> > strace -f <anything>
>
> I can't reproduce. Can you send me your config?
>
sure, attached.
-ss
View attachment ".config" of type "text/plain" (81421 bytes)
Powered by blists - more mailing lists