linux-kernel - Re: Boot failure with ext2 and initrds

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]

Message-ID: <Pine.LNX.4.64.0611151549130.18096@blonde.wat.veritas.com>
Date:	Wed, 15 Nov 2006 15:56:58 +0000 (GMT)
From:	Hugh Dickins <hugh@...itas.com>
To:	"Martin J. Bligh" <mbligh@...igh.org>
cc:	Andrew Morton <akpm@...l.org>, Mel Gorman <mel@...net.ie>,
	linux-kernel@...r.kernel.org
Subject: Re: Boot failure with ext2 and initrds

On Wed, 15 Nov 2006, Martin J. Bligh wrote:
> Hugh Dickins wrote:
> > 
> > i386 and ppc64 still doing builds, but after an hour on x86_64,
> > an ld got stuck in a loop under ext2_try_to_allocate_with_rsv,
> > alternating between ext2_rsv_window_add and rsv_window_remove.
> 
> Ugh. What test are you doing? kernel compile in a tight loop forever?

That kind of thing, yes: my usual test, two repeated make -j20s of
a smallish kernel in 512MB RAM + 1or2GB swap, one in a tmpfs and
one in an ext2 backed by a looped tmpfs file.  (When things go
badly wrong, little harm befalls the hard disk.)

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