linux-kernel - Re: [PATCH 1/2] ipc/sem.c: Race in sem

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]

Date:	Sun, 15 Sep 2013 12:30:00 -0700
From:	Davidlohr Bueso <davidlohr@...com>
To:	Manfred Spraul <manfred@...orfullife.com>
Cc:	Mike Galbraith <efault@....de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Rik van Riel <riel@...hat.com>,
	Davidlohr Bueso <davidlohr.bueso@...com>, hhuang@...hat.com,
	Greg KH <greg@...ah.com>
Subject: Re: [PATCH 1/2] ipc/sem.c: Race in sem_lock()

On Sun, 2013-09-15 at 13:34 +0200, Manfred Spraul wrote:
> Hi all,
> 
> On 09/15/2013 08:09 AM, Mike Galbraith wrote:
> > On Sat, 2013-09-14 at 23:34 +0200, Manfred Spraul wrote:
> >
> >> The bug is probably also present in 3.10 and 3.11, but for these kernels
> >> is is probably simpler just to move the test of sma->complex_count after
> >> the spin_is_locked() test.
> > IMHO, your 6 patch series should go to stable as well.  Scalability is
> > still BAD without them.  Now, you've shown the lock split to be buggy.
> >
> > Logically, the whole thing should be reverted entirely in stable, or
> > fixed up properly.
> Davidlohr: Are you working on fixing the open issues?

I have the patches but we're waiting for input from James to see if we
can use rcu to free the security data, which is probably the best way to
go.

Thanks,
Davidlohr

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