summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/abort.c
diff options
context:
space:
mode:
authorrodrigc <rodrigc@FreeBSD.org>2007-01-06 20:46:02 +0000
committerrodrigc <rodrigc@FreeBSD.org>2007-01-06 20:46:02 +0000
commita533f9bcf630791d3f0d1f3537afbae114d8f145 (patch)
treeec58232f798b513b925dc497192dbd72e8a14e5f /lib/libc/stdlib/abort.c
parent9131a172735d17248d28f501ef0eb37ef082434f (diff)
downloadFreeBSD-src-a533f9bcf630791d3f0d1f3537afbae114d8f145.zip
FreeBSD-src-a533f9bcf630791d3f0d1f3537afbae114d8f145.tar.gz
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>
Diffstat (limited to 'lib/libc/stdlib/abort.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud