lkml.org 
[lkml]   [2014]   [Apr]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [3.15-rc3] rtmutex-debug assertion.
On Tue, 29 Apr 2014, Dave Jones wrote:
> This is trickier to reproduce than it first seemed, as logging slows
> things down so much. But after a few hours, it logged that the
> call that triggered this was..
>
> futex(uaddr=0x7f55ff8c4000, op=0x6, val=0x200000006223800b, utime=0x7f55ff8c4000, uaddr2=0x7f55ff8c4000, val3=-123)
>
> Those addresses come from an mmap we made on startup..
>
> [init] mapping[3]: (zeropage PROT_READ | PROT_WRITE) 0x7f55ff8c4000 (1MB)
>
> op = FUTEX_LOCK_PI
>
> val seems to be garbage.
>
> I'll do another run, just to see if it's always the same set of values,
> but it's going to probably take an overnight run.

Do you have the full fuzzing log, so I can see what happened
before/around that?

Thanks,

tglx


\
 
 \ /
  Last update: 2014-04-30 11:21    [W:0.067 / U:0.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site