linux-kernel - Re: early exception error

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:	Tue, 30 Dec 2008 17:39:29 -0800 (PST)
From:	david@...g.hm
To:	Andi Kleen <andi@...stfloor.org>
cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: early exception error

On Wed, 31 Dec 2008, Andi Kleen wrote:

> david@...g.hm writes:
>>
>> doing a grep through System.map for the address that appears in the
>> error returns nothing
>
> This might be obvious, but you can't grep directly for these addresses
> because System.map contains the starting addresses of functions only
> and normally the reported address is somewhere in the middle of a
> function. So you instead have to look for the highest number lower or equal
> the address from the exception.

thanks, this was not obvious to me

the -2 error maps to

ffffffff8099e4c1 T free_bootmem_node
ffffffff8099e4e5 t alloc_bootmem_core
ffffffff8099e774 t ___alloc_bootmem_nopanic


the first error maps to

ffffffff809c2de4 T free_bootmem_node
ffffffff809c2e08 t alloc_bootmem_core
ffffffff809c3097 t ___alloc_bootmem_nopanic


so it looks like this is in alloc_bootmem_core in both cases.

David Lang
--
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/