forked from TrueCloudLab/distribution
258345ba0d
In some conditions, regulator.exit may not send a signal to blocked regulator.enter. Let's assume we are in the critical section of regulator.exit and r.available is equal to 0. And there are three more gorotines. One goroutine also executes regulator.exit and waits for the lock. Rest run regulator.enter and wait for the signal. We send the signal, and after releasing the lock, there will be lock contention: 1. Wait from regulator.enter 2. Lock from regulator.exit If the winner is Lock from regulator.exit, we will not send another signal to unlock the second Wait. Signed-off-by: Oleg Bulatov <obulatov@redhat.com> |
||
|---|---|---|
| .. | ||
| azure | ||
| base | ||
| factory | ||
| filesystem | ||
| gcs | ||
| inmemory | ||
| middleware | ||
| oss | ||
| s3-aws | ||
| s3-goamz | ||
| swift | ||
| testdriver | ||
| testsuites | ||
| fileinfo.go | ||
| storagedriver.go | ||