Brian Behlendorf 8926ab7a50 Move cv_destroy() outside zp->z_range_lock() ... With the recent SPL change (d599e4fa) that forces cv_destroy() to block until all waiters have been woken. It is now unsafe to call cv_destroy() under the zp->z_range_lock() because it is used as the condition variable mutex. If there are waiters cv_destroy() will block until they wake up and aquire the mutex. However, they will never aquire the mutex because cv_destroy() will not return allowing it's caller to drop the lock. Deadlock. To avoid this cv_destroy() is now run asynchronously in a taskq. This solves two problems: 1) It is no longer run under the zp->z_range_lock so no deadlock. 2) Since cv_destroy() may now block we don't want this slowing down zfs_range_unlock() and throttling the system. This was not as much of an issue under OpenSolaris because their cv_destroy() implementation does not do anything. They do however risk a bad paging request if cv_destroy() returns, the memory holding the condition variable is free'd, and then the waiters wake up and try to reference it. It's a very small unlikely race, but it is possible.		2011-02-10 09:27:21 -08:00
..
avl	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
nvpair	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
unicode	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00
zcommon	Add basic uio support	2011-02-10 09:21:43 -08:00
zfs	Move cv_destroy() outside zp->z_range_lock()	2011-02-10 09:27:21 -08:00
zpios	Linux 2.6.36 compat, use fops->unlocked_ioctl()	2010-11-10 17:01:08 -08:00
.gitignore	Add .gitignore files to exclude build products	2010-01-08 11:35:17 -08:00
Makefile.in	Support custom build directories and move includes	2010-09-08 12:38:56 -07:00