Brian Behlendorf d599e4fa79 Block in cv_destroy() on all waiters ... Previously we would ASSERT in cv_destroy() if it was ever called with active waiters. However, I've now seen several instances in OpenSolaris code where they do the following: cv_broadcast(); cv_destroy(); This leaves no time for active waiters to be woken up and scheduled and we trip the ASSERT. This has not been observed to be an issue on OpenSolaris because their cv_destroy() basically does nothing. They still do run the risk of the memory being free'd after the cv_destroy() and hitting a bad paging request. But in practice this race is so small and unlikely it either doesn't happen, or is so unlikely when it does happen the root cause has not yet been identified. Rather than risk the same issue in our code this change updates cv_destroy() to block until all waiters have been woken and scheduled. This may take some time because each waiter must acquire the mutex. This change may have an impact on performance for frequently created and destroyed condition variables. That however is a price worth paying it avoid crashing your system. If performance issues are observed they can be addressed by the caller.		2011-02-04 14:09:08 -08:00
..
spl	Block in cv_destroy() on all waiters	2011-02-04 14:09:08 -08:00
splat	Remove VN_HOLD/VN_RELE/VOP_PUTPAGE	2011-01-12 11:38:05 -08:00
.gitignore	sun-misc-gitignore	2010-01-08 09:37:54 -08:00
Makefile.in	Support custom build directories	2010-09-05 21:49:05 -07:00