linux-kernel - Re: mmotm 2010-11-23 + autogroups -> inconsistent lock state

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] [day] [month] [year] [list]

Message-Id: <1291348702.7633.33.camel@marge.simson.net>
Date:	Fri, 03 Dec 2010 04:58:22 +0100
From:	Mike Galbraith <efault@....de>
To:	paulmck@...ux.vnet.ibm.com
Cc:	Valdis.Kletnieks@...edu, akpm@...ux-foundation.org,
	Ingo Molnar <mingo@...e.hu>, mm-commits@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: mmotm 2010-11-23 + autogroups -> inconsistent lock state

On Thu, 2010-12-02 at 10:16 -0800, Paul E. McKenney wrote:
> On Wed, Nov 24, 2010 at 01:25:25PM -0700, Mike Galbraith wrote:
>  
> > Despite task groups being freed via rcu, update_shares_cup() hits freed
> > memory and explodes, and nothing I've tried has been able to stop it.
> > The only thing I haven't tried (aside from the right thing;) is to take
> > rcu out of the picture entirely.
> 
> Is your new autogroup structure retaining a pointer to memory that
> is freed by RCU?

That turned out to be a typo that left freed cfs_rq registered.  No dark
elves (memory ordering), just a defenseless little typo.

	-Mike

--
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/