linux-kernel - Re: /proc/kallsyms broken in 2.6.26-rc1-git6

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:	Mon, 12 May 2008 11:00:32 +0100
From:	Paulo Marques <pmarques@...popie.com>
To:	Alexey Dobriyan <adobriyan@...il.com>
CC:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: /proc/kallsyms broken in 2.6.26-rc1-git6

Alexey Dobriyan wrote:
> On Fri, May 09, 2008 at 08:59:56PM +0100, Paulo Marques wrote:
>> Andi Kleen wrote:
>>>[...]
>>> Yes and? Surely that's not correct?
>> That's not for me to judge, but I believe it has always been like that.
> 
> *cough*
> 
> Here is how typical /proc/kallsyms looks like:
> 
> ffffffff80200000 A _text
> ffffffff80200000 T startup_64
> ffffffff802000b7 t ident_complete
> ffffffff80200100 T secondary_startup_64

This isn't helpful... the question is whether it is kallsyms misbehaving 
and placing new symbols in the kernel image or if it is some other 
change in the kernel that is generating new symbols that end up in the 
symbol table.

My guess it is that it is the later, and in that case, from a kallsyms 
standpoint "it has always been like that".

-- 
Paulo Marques - www.grupopie.com

"God is love. Love is blind. Ray Charles is blind. Ray Charles is God."
--
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/