Konstantin Belousov cc3d8c35f5 There are several code sequences like ... vfs_busy(mp); vfs_write_suspend(mp); which are problematic if other thread starts unmount between two calls. The unmount starts a write, while vfs_write_suspend() drain writers. On the other hand, unmount drains busy references, causing the deadlock. Add a flag argument to vfs_write_suspend and require the callers of it to specify VS_SKIP_UNMOUNT flag, when the call is performed not in the mount path, i.e. the covered vnode is not locked. The suspension is not attempted if VS_SKIP_UNMOUNT is specified and unmount is in progress. Reported and tested by: Andreas Longwitz <longwitz@incore.de> Sponsored by: The FreeBSD Foundation MFC after: 3 weeks		2013-07-09 20:49:32 +00:00
..
ffs	There are several code sequences like	2013-07-09 20:49:32 +00:00
ufs	Don't assume that UFS on-disk format of a directory is the same as	2013-07-01 04:06:40 +00:00