| 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
| ||
|
Message-ID: <20120503170101.GF2592@linux.vnet.ibm.com> Date: Thu, 3 May 2012 10:01:01 -0700 From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> To: Sasha Levin <levinsasha928@...il.com> Cc: "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org> Subject: Re: rcu: BUG on exit_group On Thu, May 03, 2012 at 05:55:14PM +0200, Sasha Levin wrote: > On Thu, May 3, 2012 at 5:41 PM, Paul E. McKenney > <paulmck@...ux.vnet.ibm.com> wrote: > > On Thu, May 03, 2012 at 10:57:19AM +0200, Sasha Levin wrote: > >> Hi Paul, > >> > >> I've hit a BUG similar to the schedule_tail() one when. It happened > >> when I've started fuzzing exit_group() syscalls, and all of the traces > >> are starting with exit_group() (there's a flood of them). > >> > >> I've verified that it indeed BUGs due to the rcu preempt count. > > > > Hello, Sasha, > > > > Which version of -next are you using? I did some surgery on this > > yesterday based on some bugs Hugh Dickins tracked down, so if you > > are using something older, please move to the current -next. > > I'm using -next from today (3.4.0-rc5-next-20120503-sasha-00002-g09f55ae-dirty). Hmmm... Looking at this more closely, it looks like there really is an attempt to acquire a mutex within an RCU read-side critical section, which is illegal. Could you please bisect this? 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/
Powered by blists - more mailing lists