Re: SyS symbol munging.

From: Andrew Morton
Date: Fri May 10 2013 - 15:35:25 EST


On Fri, 10 May 2013 15:24:17 -0400 Dave Jones <davej@xxxxxxxxxx> wrote:

> On Fri, May 10, 2013 at 12:14:54PM -0700, Andrew Morton wrote:
>
> > [ 163.953629] Call Trace:
> > [ 163.957706] [<ffffffff812be322>] ipcget+0x182/0x380
> > [ 163.962123] [<ffffffff810b99a5>] ?trace_hardirqs_on_caller+0x115/0x1e0
> > [ 163.966752] [<ffffffff812c559a>] SyS_shmget+0x5a/0x60
> > [ 163.971163] [<ffffffff812c47e0>] ? shm_close+0x140/0x140
> > [ 163.975590] [<ffffffff812c3e60>] ? shm_release+0x50/0x50
> > [ 163.979991] [<ffffffff812c3df0>] ? shm_get_unmapped_area+0x20/0x20
> > [ 163.984499] [<ffffffff816caa14>] tracesys+0xdd/0xe2
>
> This has been bugging me for a while.
> What's changing sys_shmget to SyS_shmget in that trace ? And why ?
>

nm vmlinux | grep SyS

That's the actual name of the function definition which the C compiler
sees. It's emitted by SYSCALL_DEFINE, cooked up by all the macro goop
in include/linux/syscalls.h.

I forget who did this initially and peeling back those layers with git
is tiresome.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/