diff options
| author | Nick Piggin <npiggin@kernel.dk> | 2010-11-25 12:47:15 +0200 |
|---|---|---|
| committer | Boaz Harrosh <bharrosh@panasas.com> | 2011-03-15 15:02:50 +0200 |
| commit | 97178b7b6c84bd14660b89474d27931a1ea65c66 (patch) | |
| tree | b763cc48e6456b944e7bed877ad2a996809124eb /fs/exofs/inode.c | |
| parent | a8f1418f9e9bd4c487a7b703ff26c5dd5ceb2bf3 (diff) | |
| download | op-kernel-dev-97178b7b6c84bd14660b89474d27931a1ea65c66.zip op-kernel-dev-97178b7b6c84bd14660b89474d27931a1ea65c66.tar.gz | |
exofs: simple fsync race fix
It is incorrect to test inode dirty bits without participating in the inode
writeback protocol. Inode writeback sets I_SYNC and clears I_DIRTY_?, then
writes out the particular bits, then clears I_SYNC when it is done. BTW. it
may not completely write all pages out, so I_DIRTY_PAGES would get set
again.
This is a standard pattern used throughout the kernel's writeback caches
(I_SYNC ~= I_WRITEBACK, if that makes it clearer).
And so it is not possible to determine an inode's dirty status just by
checking I_DIRTY bits. Especially not for the purpose of data integrity
syncs.
Missing the check for these bits means that fsync can complete while
writeback to the inode is underway. Inode writeback functions get this
right, so call into them rather than try to shortcut things by testing
dirty state improperly.
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
Diffstat (limited to 'fs/exofs/inode.c')
| -rw-r--r-- | fs/exofs/inode.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/exofs/inode.c b/fs/exofs/inode.c index c8f58a9..fb9d380 100644 --- a/fs/exofs/inode.c +++ b/fs/exofs/inode.c @@ -1290,7 +1290,8 @@ out: int exofs_write_inode(struct inode *inode, struct writeback_control *wbc) { - return exofs_update_inode(inode, wbc->sync_mode == WB_SYNC_ALL); + /* FIXME: fix fsync and use wbc->sync_mode == WB_SYNC_ALL */ + return exofs_update_inode(inode, 1); } /* |
