Christoph Hellwig <[email protected]> wrote:
>
> On Fri, Mar 17, 2006 at 07:09:14PM +0000, Eric Van Hensbergen wrote:
> > Subject: [PATCH] print v9fs module address
> > From: Latchesar Ionkov <[email protected]>
> > Date: 1141313037 -0500
> >
> > This patch prints v9fs module address when the module is initialized. It is
> > useful to have it in the logs -- if the kernel crashes the address can be
> > used together with the oops print to find out the exact place (presumably in
> > the v9fs code) that cause the oops.
>
> NACK.
>
> This just clutters the log. The information is provided in /proc/modules
> for all modules.
But it's not printed out in an oops record and it can be hard to read
/proc/modules when the kernel is dead.
That being said...
If we really want this info then it should be printed out by the oops code,
where it prints the names of all the loaded modules - add "(0xc0123456)"
after each module name.
But I can't say I've ever felt a need for this feature - the symbolic info
in the oops trace tells you function_name+0xoffset/0xsize [*] which is
sufficient info for debugging.
IOW: what's the use case here, Eric?
[*] unless it's x86_64, which randomly prints some of these things in
decimal or sanskrit or something.
-
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/
[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]
