summaryrefslogtreecommitdiffstats
path: root/sys/kern
diff options
context:
space:
mode:
authormav <mav@FreeBSD.org>2014-10-28 08:00:28 +0000
committermav <mav@FreeBSD.org>2014-10-28 08:00:28 +0000
commit928386888ba740d10d5891223be7757b5099e310 (patch)
tree6e9d0c02593ee1e606cce9c9a43e7f0d5e3ab879 /sys/kern
parent1c649cc8f3b5376126d2ea329e6f4badebe7f008 (diff)
downloadFreeBSD-src-928386888ba740d10d5891223be7757b5099e310.zip
FreeBSD-src-928386888ba740d10d5891223be7757b5099e310.tar.gz
MFC r273638:
Revert somewhat hackish geom_disk optimization, committed as part of r256880, and the following r273143 commit, supposed to workaround introduced issue by quite innocent-looking change. While there is no clear understanding why, but r273143 is accused in data corruption in some environments with high I/O load. I personally don't see any problem in that commit, and possibly it is just a trigger to some other bug somewhere, but better safe then sorry for now. Requested by: scottl@
Diffstat (limited to 'sys/kern')
-rw-r--r--sys/kern/vfs_bio.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/sys/kern/vfs_bio.c b/sys/kern/vfs_bio.c
index 8f6a3c3..cc6ac46 100644
--- a/sys/kern/vfs_bio.c
+++ b/sys/kern/vfs_bio.c
@@ -3585,8 +3585,10 @@ biodone(struct bio *bp)
bp->bio_flags |= BIO_DONE;
wakeup(bp);
mtx_unlock(mtxp);
- } else
+ } else {
+ bp->bio_flags |= BIO_DONE;
done(bp);
+ }
}
/*
OpenPOWER on IntegriCloud