linux-kernel - Re: 2.6.29-rc5 hanging at boot when CONFIG_LOCK

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

Date:	Mon, 16 Feb 2009 11:51:22 -0800
From:	"Adam J. Richter" <adam@...drasil.com>
To:	Ingo Molnar <mingo@...e.hu>, peterz@...radead.org
Cc:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: 2.6.29-rc5 hanging at boot when CONFIG_LOCK_STAT=y

On Mon, Feb 16, 2009 at 01:29:12PM +0100, Ingo Molnar wrote:
> 
> * Adam J. Richter <adam@...drasil.com> wrote:
> 
> > Hello Peter and Ingo,
> > 
> > 	Under linux-2.6.29-rc5, and I believe all earlier 2.6.29-rc
> > releases, CONFIG_LOCK_STAT=y causes my system to hang at boot when
> > booting from lilo-22.8.  Linux-2.6.28 does not have this hang.
> > Disabling LOCK_STAT or booting from grub avoids the hang.  [...]
> 
> hm, so if booting from LILO you see a hang, while when booting with GRUB 
> it works fine?
> 
> Could it be LILO messing up the kernel image loading somehow? LOCK_STAT 
> might just be the thing that brings the kernel over a specific size.
> 
> 	Ingo

	Thank you for your prompt responses, Peter and Ingo.

	I have a little more information to add, which is consistent
with but not does not prove your theory that kernel size is
the trigger.

	What I said about the hangs occuring in all 2.6.29-rc versions
was incorrect.  I just retried 2.6.29-rc1, rc2 and rc3, all with
LOCK_STAT=y, and only rc3 hung.  Here is the information that "size"
returns about these kernels, along with rc5 compiled with LOCK_STAT=n
(although I am not sure exactly which ELF sections it classifies as
text, data and bss).

   text    data     bss     dec   version	    LOCK_STAT	behavior
3612151 1803760 4530176 9946087   linux-2.6.29-rc1  Y           boots
3612498 1802768 4530176 9945442   linux-2.6.29-rc2  Y           boots
3831641 1802920 4530176 10164737  linux-2.6.29-rc3  Y           hangs
3825876  485816 4255744 8567436   linux-2.6.29-rc5  N           boots

	 Your theory may be right, although I would think that my
experiments in splicing together .config files that did and did not
have this problem would have produced some smaller kernels that had
the problem, given that the configuration that did not hang was much
smaller.  However, I do not have those kernel images handy to test,
and I do not have time to do a lot of recompilations right now.
Perhaps late tonight I may try some more experiments.

	Thanks again for your responses.

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