lkml.org 
[lkml]   [2014]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: mm/sched/net: BUG when running simple code
On Mon, Jun 16, 2014 at 11:17:55PM -0400, Sasha Levin wrote:
> On 06/13/2014 12:13 AM, Dave Jones wrote:
> > On Fri, Jun 13, 2014 at 12:01:37AM -0400, Sasha Levin wrote:
> > another theory: Trinity can sometimes generate plausible looking module
> > addresses and pass those in structs etc.
> >
> > I wonder if there's somewhere in that path that isn't checking that the address
> > in the optval it got is actually a userspace address before it tries to write to it.
>
> It happened again, and this time I've left the kernel addresses in, and it's quite
> interesting:
>
> [ 88.837926] Call Trace:
> [ 88.837926] [<ffffffff9ff6a792>] __sock_create+0x292/0x3c0
> [ 88.837926] [<ffffffff9ff6a610>] ? __sock_create+0x110/0x3c0
> [ 88.837926] [<ffffffff9ff6a920>] sock_create+0x30/0x40
> [ 88.837926] [<ffffffff9ff6ad4c>] SyS_socket+0x2c/0x70
> [ 88.837926] [<ffffffffa0561c30>] ? tracesys+0x7e/0xe6
> [ 88.837926] [<ffffffffa0561c93>] tracesys+0xe1/0xe6
>
> tracesys() seems to live inside a module space here?

I think it's more likely kASLR. The Documentation/x86/x86_64/mm.txt doc needs updating.

--
Dan Aloni


\
 
 \ /
  Last update: 2014-06-17 07:21    [W:0.044 / U:2.324 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site