Craig Rodrigues 82c59ec651 When performing a mount update to change a mount from read-only to read-write, ... do not call markvoldirty() until the mount has been flagged as read-write. Due to the nature of the msdosfs code, this bug only seemed to appear for FAT-16 and FAT-32. This fixes the testcase: #!/bin/sh dd if=/dev/zero bs=1m count=1 oseek=119 of=image.msdos mdconfig -a -t vnode -f image.msdos newfs_msdos -F 16 /dev/md0 fd120m mount_msdosfs -o ro /dev/md0 /mnt mount | grep md0 mount -u -o rw /dev/md0; echo $? mount | grep md0 umount /mnt mdconfig -d -u 0 PR: 105412 Tested by: Eugene Grosbein <eugen grosbein pp ru>		2007-01-06 20:46:02 +00:00
..
bootsect.h
bpb.h	Eliminate obsolete comment, now that getushort() is implemented in	2007-01-05 05:28:57 +00:00
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	When performing a mount update to change a mount from read-only to read-write,	2007-01-06 20:46:02 +00:00
msdosfs_vnops.c	o Do not leave uninitialized birthtime: in MSDOSFSMNT_LONGNAME	2006-12-03 19:04:26 +00:00
msdosfsmount.h