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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
