« Previous | Next » 

Revision 8d7d8b57

ID8d7d8b570a42e7d90b290ca4bb40684adf72d4ef
Parent 26082b7e
Child 70567db0

Added by Michael Hanselmann about 12 years ago

locking: Handle spurious notifications on lock acquire

This was already a TODO since the implementation of lock priorities in
September 2010. Under certain conditions a waiting acquire can be
notified at a time when it can't actually get the lock. In this case it
would try and fail to acquire the lock and then return to the caller
before the timeout ends.

While this is not bad (nothing breaks), it isn't nice either. A separate
patch will prevent unnecessary notifications when shared locks are
released.

Signed-off-by: Michael Hanselmann <>
Reviewed-by: Bernardo Dal Seno <>

Files

  • added
  • modified
  • copied
  • renamed
  • deleted

View differences