Konstantin Belousov b2344ab5ff Do not call VFS_SYNC() before VFS_UNMOUNT() for forced unmount. ... Since VFS does not/cannot stop writes, sync might run indefinitely, or be a wrong thing to do at all. E. g. NFS ignores VFS_SYNC() for forced unmounts, since non-responding server does not allow sync to finish. On the other hand, filesystems can and do stop writes using fs-specific facilities, and should already fully flush caches in VFS_UNMOUNT() due to the race. Adjust msdosfs tp sync in unmount for forced call, to accomodate the new behaviour. Note that it is still racy, since writes are not stopped. Discussed with: avg, bjk, mckusick Reported and tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 3 weeks		2014-12-09 10:00:47 +00:00
..
bootsect.h
bpb.h
denode.h
direntry.h
fat.h
msdosfs_conv.c
msdosfs_denode.c
msdosfs_fat.c
msdosfs_fileno.c
msdosfs_iconv.c
msdosfs_lookup.c
msdosfs_vfsops.c
msdosfs_vnops.c
msdosfsmount.h