Konstantin Belousov 63876b3ba2 On rename, do not perform truncation of dirhash if the vnode ... truncation failed. Doing so resulted in inconsistent state of the ufs dirhash with regard to the actual directory inode state, and could lead to spurious ENOENT errors for lookups of existing files in production kernels, or assertion failures in the debugging kernels. Change the logic of calling ufsdirhash_dirtrunc() to be same as in ufs_direnter(). Execute UFS_TRUNCATE() first, log error, and only do dirtrunc() if UFS_TRUNCATE() succeeded. Note that the problem was exacerbated by the bug in the flush_newblk_dep() function (see r305599), which caused in the spurios errors from ffs_sync() and then ffs_truncate(). In collaboration with: pho Reviewed by: mckusick Sponsored by: The FreeBSD Foundation MFC after: 2 weeks		2016-09-08 12:09:34 +00:00
..
ffs	Do not leak transient ENOLCK error from flush_newblk_dep() loop.	2016-09-08 12:08:54 +00:00
ufs	On rename, do not perform truncation of dirhash if the vnode	2016-09-08 12:09:34 +00:00