Re: 2.5.44: How to decode call trace

From: Andi Kleen (
Date: Tue Oct 22 2002 - 22:50:41 EST

Olaf Dietsche <> writes:
> and this is the code:
> static int __fscap_lookup(struct vfsmount *mnt, struct nameidata *nd)
> {
> static char name[] = ".capabilities";
> nd->mnt = mntget(mnt);
> nd->dentry = dget(mnt->mnt_sb->s_root);
> nd->flags = 0;
> return path_walk(name, nd);
> }
> What does .text.lock.namei and name.810 mean?

.text.lock.namei means that it hung in the slow path of a spinlock that
is referenced from namei.c

name.810 is a static data variable, probably the static char name[]
shown above. Remember the kernel backtrace is not exact and can print
random stack junk that looks like return addresses too. You always have
to sanity check each entry.

> Is there a way to get the line number out of these hex values?

addr2line -e vmlinux ... does this when you compile the kernel with -g

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:01:02 EST