linux-kernel - Re: 2.6.35-rc3 deadlocks on semaphore operations

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:	Mon, 21 Jun 2010 09:31:10 -0500 (CDT)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Manfred Spraul <manfred@...orfullife.com>
cc:	linux-kernel@...r.kernel.org, Julia Lawall <julia@...u.dk>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: 2.6.35-rc3 deadlocks on semaphore operations

On Sat, 19 Jun 2010, Manfred Spraul wrote:

> Hello Christoph,
>
> On 06/18/2010 04:56 PM, Christoph Lameter wrote:
> > One important fact that I forgot to mention: This is on a dual quad core
> > dell box (8 hardware threads) with CONCURRENCY_LEVEL set to 9.
> >
>
> - Which version of make do you use? That would be one suspect that might use
> semop().

$ make --version
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for x86_64-pc-linux-gnu

> - If I run make -j5 bzImage, then no semaphore arrays are used.
> Could you try to figure out which executable is doing the 'semop()' call?

Looks like this was ld

> Or: what's the output of ps xawwwww_

Need to do another run with a broken kernel for this.
--
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/