lkml.org 
[lkml]   [2013]   [May]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: SyS symbol munging.
On Fri, May 10, 2013 at 03:24:17PM -0400, Dave Jones 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 ?

+1.

And not only sys_shmget:

SyS_access
SyS_chdir
SyS_chown
SyS_fchownat
SyS_flock
SyS_mkdir
SyS_mkdirat
SyS_mknod
SyS_mknodat
SyS_mount

I have those in backtraces from my boot logs of randconfig kernels in
the last couple of days.

--
Regards/Gruss,
Boris.

Sent from a fat crate under my desk. Formatting is fine.
--


\
 
 \ /
  Last update: 2013-05-10 22:01    [W:0.052 / U:0.312 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site