Patches to fix access of busy objects in ban lurker, expiry thread and EXP_NukeOne (bugs #1150 and #1162)

[Martin Blix Grydeland]

Hunting #1150 some additional areas popped up too where attempts to access
busy objects from other threads could happen, with subsequent assertion.

I have not been able to create good test cases for these, as the time
window is too small. Though all problems have been confirmed (and confirmed
fixed by the patches), by introducing deliberate delays in Varnish during
testing.

Regards,
Martin Blix Grydeland

-- 
Martin Blix Grydeland
Varnish Software AS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20120704/68ce8035/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Make-the-ban-lurker-skip-busy-objects.patch
Type: application/octet-stream
Size: 1293 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20120704/68ce8035/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Do-not-try-to-expire-objects-that-are-still-busy.patch
Type: application/octet-stream
Size: 1222 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20120704/68ce8035/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-Do-not-consider-busy-objects-as-candidates-in-EXP_Nu.patch
Type: application/octet-stream
Size: 1065 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20120704/68ce8035/attachment-0002.obj>