lowLock must be locked before highLock in the queue #5

zeripath · 2021-08-14T09:30:18Z

zeripath commented

2021-08-14 09:30:18 +00:00

Unfortunately the locking order in the queue.Close() function is
incorrect as the queue.Len() function locks the lowLock before the
highLock. We therefore must lock the lowLock before the highLock.

Signed-off-by: Andrew Thornton art27@cantab.net

Unfortunately the locking order in the queue.Close() function is incorrect as the queue.Len() function locks the lowLock before the highLock. We therefore must lock the lowLock before the highLock. Signed-off-by: Andrew Thornton <art27@cantab.net>

zeripath added 1 commit 2021-08-14 09:30:18 +00:00

lowLock must be locked before highLock in the queue

Unfortunately the locking order in the queue.Close() function is
incorrect as the queue.Len() function locks the lowLock before the
highLock.  We therefore must lock the lowLock before the highLock.

Signed-off-by: Andrew Thornton <art27@cantab.net>

continuous-integration/drone/pr Build is passing

Details

604fc041ac

lunny approved these changes 2021-08-14 13:14:21 +00:00

lunny merged commit 47d1e224cd into master

2021-08-14 13:14:25 +00:00

lunny referenced this issue from a commit

2021-08-14 13:14:25 +00:00

lowLock must be locked before highLock in the queue (#5)

Sign in to join this conversation.

No reviewers