/proc/kallsyms and symbol size

Hello,

Many monitoring tools use /proc/kallsyms to build a symbol table for the kernel.
This technique has the advantage that it does not require root privileges, nor
an up-to-date /boot/System.map, nor a decompressed kernel in /boot.

The problem is that /proc/kallsyms does not report the size of the symbols.
Yet, the information is available in the kernel as it is used by functions such
as __print_symbol(). Having the size is useful to correlate the address obtained
is a sample with a symbol name. Most tools use an approximation which assumes
symbols are contiguous to estimate the size.

Apart from the backward compatbility problem for the output of kallsyms, what
would be the major issue with exposing this information?

Thanks.

-- 
-Stephane
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: /proc/kallsyms and symbol size
    • From: Paulo Marques <[email protected]>

• Prev by Date: [PATCH] sched: cleanup adjusting sched_class
• Next by Date: libata broken on Pegasos PPC platform (was: Re: IDE broken on Pegasos PPC platform)
• Previous by thread: [PATCH] sched: cleanup adjusting sched_class
• Next by thread: Re: /proc/kallsyms and symbol size
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]