Re: [RFC][PATCH] fixup pi_state in futex_requeue on lock steal
From: Ingo Molnar <hidden>
Date: 2009-08-08 15:28:49
Also in:
lkml
From: Ingo Molnar <hidden>
Date: 2009-08-08 15:28:49
Also in:
lkml
* Darren Hart [off-list ref] wrote:
So, I think we're fine with respect to the pi_state ownership! In fact I finally managed to catch the lock steal in the requeue loop in my tracing, and everything worked fine. Going to go rerun a bunch more tests and see if I hit any other issues, if I do, I suspect they are unrelated to this. Thanks for the help in thinking this through.
i've got these queued up: 00235fe: futex: Update woken requeued futex_q lock_ptr 1bbf208: rtmutex: Avoid deadlock in rt_mutex_start_proxy_lock() should i drop them? Ingo