summaryrefslogtreecommitdiffstats
path: root/sys/kern/vfs_vnops.c
diff options
context:
space:
mode:
authormckusick <mckusick@FreeBSD.org>2002-10-25 00:20:37 +0000
committermckusick <mckusick@FreeBSD.org>2002-10-25 00:20:37 +0000
commit6b1611bd949afb58a84ad54e4bbcf960b0ef28b1 (patch)
tree3538f027616418c955bda99415bbb0b81e6d64b5 /sys/kern/vfs_vnops.c
parent776a2129fe77eb14c0d61bf67d393ee4893c4a08 (diff)
downloadFreeBSD-src-6b1611bd949afb58a84ad54e4bbcf960b0ef28b1.zip
FreeBSD-src-6b1611bd949afb58a84ad54e4bbcf960b0ef28b1.tar.gz
Within ufs, the ffs_sync and ffs_fsync functions did not always
check for and/or report I/O errors. The result is that a VFS_SYNC or VOP_FSYNC called with MNT_WAIT could loop infinitely on ufs in the presence of a hard error writing a disk sector or in a filesystem full condition. This patch ensures that I/O errors will always be checked and returned. This patch also ensures that every call to VFS_SYNC or VOP_FSYNC with MNT_WAIT set checks for and takes appropriate action when an error is returned. Sponsored by: DARPA & NAI Labs.
Diffstat (limited to 'sys/kern/vfs_vnops.c')
-rw-r--r--sys/kern/vfs_vnops.c11
1 files changed, 8 insertions, 3 deletions
diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c
index 08f8093..0281a29 100644
--- a/sys/kern/vfs_vnops.c
+++ b/sys/kern/vfs_vnops.c
@@ -1005,19 +1005,24 @@ vn_finished_write(mp)
/*
* Request a filesystem to suspend write operations.
*/
-void
+int
vfs_write_suspend(mp)
struct mount *mp;
{
struct thread *td = curthread;
+ int error;
if (mp->mnt_kern_flag & MNTK_SUSPEND)
- return;
+ return (0);
mp->mnt_kern_flag |= MNTK_SUSPEND;
if (mp->mnt_writeopcount > 0)
(void) tsleep(&mp->mnt_writeopcount, PUSER - 1, "suspwt", 0);
- VFS_SYNC(mp, MNT_WAIT, td->td_ucred, td);
+ if ((error = VFS_SYNC(mp, MNT_WAIT, td->td_ucred, td)) != 0) {
+ vfs_write_resume(mp);
+ return (error);
+ }
mp->mnt_kern_flag |= MNTK_SUSPENDED;
+ return (0);
}
/*
OpenPOWER on IntegriCloud