linux-kernel - Re: Bug report : reproducible memory allocator bug in 2.6.19.2

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

Message-ID: <45BD06AC.1080008@mbligh.org>
Date:	Sun, 28 Jan 2007 12:25:16 -0800
From:	"Martin J. Bligh" <mbligh@...igh.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	linux-kernel@...r.kernel.org, Andrew Morton <akpm@...l.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Bug report : reproducible memory allocator bug in 2.6.19.2

Mathieu Desnoyers wrote:
> Hi,
> 
> Trying to build cross-compilers (or kernels) on a 2-way x86_64 (amd64) with
> make -j3 triggers the following OOPS after about 30 minutes on
> 2.6.19.2. Due to the amount of time and the heavy load it takes before it
> happens, I suspect a race condition. Memtest86 tests passed ok. The
> amount of swap used when the condition happens is about 52k and stable
> (only ~800MB/1GB are used).
> 
> I am going to give it a look, but I suspect you might help narrowing it
> down more quickly. Any insight would be appreciated.

Mmm. that's going to be messy to debug ... but didn't we already know
that kernel was racy? Or is 2.6.19.2 after that fix already? Does 20-rc6
still break?

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