Messages in this thread | | | Date | Mon, 12 May 2008 19:50:52 +0400 | From | Cyrill Gorcunov <> | Subject | Re: /proc/kallsyms broken in 2.6.26-rc1-git6 |
| |
[Paulo Marques - Mon, May 12, 2008 at 11:00:32AM +0100] > 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 > >
If it help - I've taken Andi's config, compiled the kernel and didn't find any screwed symbols (nor is System.map nor in /proc/kallsyms). The kernel - today Linus's git tree:
--- commit 492c2e476eac010962850006c49df326919b284c Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Sun May 11 17:09:41 2008 -0700
Linux 2.6.26-rc2 ---
The diff btw Andi's config and new one is:
+CONFIG_PCSPKR_PLATFORM=y -CONFIG_PCNET32_NAPI=y
- Cyrill -
| |