linux-kernel - Re: linux-next: Tree for June 23

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: <19f34abd0806231043x6f254ed1ye896b55eafec577f@mail.gmail.com>
Date:	Mon, 23 Jun 2008 19:43:16 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	"Steven Rostedt" <srostedt@...hat.com>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	"Pekka Enberg" <penberg@...helsinki.fi>,
	"Christoph Lameter" <clameter@....com>
Subject: Re: linux-next: Tree for June 23

On Mon, Jun 23, 2008 at 7:26 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
> On Mon, Jun 23, 2008 at 2:26 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
>> And additionally, the next two boots hung here (but the third one was okay):
>>
>> http://www.kernel.org/pub/linux/kernel/people/vegard/kernels/20080623-next/DSCF3015.JPG
>>
>> I don't know what these issues are related too. I can try
>> debug_initcall for the hang.
>
> The last initcall to run is populate_rootfs(), however the last
> message on the screen is "debug: unmapping init memory
> f7cb0000..f7ff0000":
>
> http://www.kernel.org/pub/linux/kernel/people/vegard/kernels/20080623-next/DSCF3016.JPG
>
> In fact, it seems to me that init memory is being unmapped before all
> initcalls have finished... that would seem disastrous.

Ah, scratch that. Digging a bit deeper, it becomes obvious that the
initramfs/initrd code is freeing its own memory using the same
function in the end (free_init_pages()) as free_initmem(), so they'll
in fact just print the same message. That doesn't change the fact of
the hang, however...

My config can be found at:

    http://www.kernel.org/pub/linux/kernel/people/vegard/kernels/20080623-next/config


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/