On 01/20/2016 09:51 PM, Jens Axboe wrote:
On 01/20/2016 09:43 PM, Bruce Cran wrote:
On 01/20/2016 09:33 PM, Jens Axboe wrote:
Can you try and revert commit 09400a60042 and see if that fixes it?
Yes, that does fix it.
So it sounds like a double unlock issue, as per the bug report you also
referenced.
Can you checkout out the 2.4 release again, and see if there are cases
where pthread_cond_timedwait() returns with the mutex unlocked already?
The man page states:
"Upon successful return, the mutex shall have been locked and shall be
owned by the calling thread."
but it's not clear if that's not the case for error return (eg timed out).
Duh, nevermind:
http://git.kernel.dk/cgit/fio/commit/?id=42e833fa08803ccea6c99df353398a7423845c51
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
