linux-kernel - Re: today's linux-next fails to boot

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:	Fri, 11 Jul 2008 16:54:04 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Török Edwin" <edwintorok@...il.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Takashi Iwai" <tiwai@...e.de>,
	linux-next@...r.kernel.org,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: today's linux-next fails to boot

On Fri, Jul 11, 2008 at 4:48 PM, Török Edwin <edwintorok@...il.com> wrote:
>> One really simple way of getting some more info out of this is to take
>> the EIP value (here c0181ca0) and run it through addr2line:
>>
>>     $ addr2line -e vmlinux -i c0181ca0
>
> Thanks for the hint, I rebuilt a failing kernel, and this is what
> addr2line says:
>
> $ addr2line -e vmlinux -i c0181ca0
>
> ??:0
> $ addr2line -e vmlinux -f c0181ca0
> kmem_cache_alloc
> ??:0

Ouch, sorry. You need CONFIG_DEBUG_INFO for this to really make any
sense. My habits are deceiving me, because I always build with
DEBUG_INFO. Ingo claims that this slows down his builds, so he never
does it. In the end, it is up to each one of us to choose his options,
but in general, I think it should be used when testing kernels.

If you're tired of rebuilding kernels now, I don't blame you. Another
lesson learned for me :-(


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