Searched hist:ae620d4480a0559ab2135510e153a77ae5568c71 (Results 1 – 1 of 1) sorted by relevance
| /freebsd/sys/fs/msdosfs/ |
| H A D | msdosfs_vfsops.c | diff ae620d4480a0559ab2135510e153a77ae5568c71 Sun Jun 29 05:05:59 CEST 2003 Tim J. Robbins <tjr@FreeBSD.org> XXX Copy workaround from UFS: open device for write access even if
the user requests a read-only mount. This is necessary because we
don't do the VOP_OPEN again if they upgrade a read-only mount to
read-write.
Fixes lockup when creating files on msdosfs mounts that have been
mounted read-only then upgraded to read-write. The exact cause of
the lockup is not known, but it is likely to be the kernel getting
stuck in an infinite loop trying to write dirty buffers to a device
without write permission.
Reported/tested by andreas, discussed with phk.
diff ae620d4480a0559ab2135510e153a77ae5568c71 Sun Jun 29 05:05:59 CEST 2003 Tim J. Robbins <tjr@FreeBSD.org> XXX Copy workaround from UFS: open device for write access even if
the user requests a read-only mount. This is necessary because we
don't do the VOP_OPEN again if they upgrade a read-only mount to
read-write.
Fixes lockup when creating files on msdosfs mounts that have been
mounted read-only then upgraded to read-write. The exact cause of
the lockup is not known, but it is likely to be the kernel getting
stuck in an infinite loop trying to write dirty buffers to a device
without write permission.
Reported/tested by andreas, discussed with phk.
|