On Fri, Aug 04, 2006 at 09:21:30AM -0700, Matthew Dillon wrote: > It looks like I copied the original bug to the new lock code when I > rewrote it during 1.5. I'm not sure when it was first introduced but > it looks like the code attempted to optimize the unblocking code by > breaking out of the loop early in certain situations, but it turns out > the optimization check it was doing was insufficient and it was breaking > out too early.
Braino. The check was the wrong way, e.g. it should check whether the range is covering the given [start, end], not the other way around. Joerg
