On Tue, Apr 29, 2014 at 07:24:30PM -0700, Davidlohr Bueso wrote:
> > futex(uaddr=0x7f55ff8c4000, op=0x6, val=0x200000006223800b,
> > utime=0x7f55ff8c4000, uaddr2=0x7f55ff8c4000, val3=-123)
>
> Perhaps because of chance. Even for pi futexes, if the lock is
> uncontended, the kernel will never take part.
Ok, once more..
futex(uaddr=0x25fe000[page_rand], op=0x6, val=0xffff4e2644b3dfcb,
utime=0x25fe004[page_rand], uaddr2=0x25fe008[page_rand],
val3=0xffffffff440fcd80)
FUTEX_LOCK_PI again.
> Would reverting commit c365c292d059 (sched: Consider pi boosting in
> setscheduler()) fix this?
I'll try and write a standalone reproducer in the morning.
Then I'll be able to tell you for sure if that commit is good/bad.
Dave
--
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/
