diff options
author | Jan Kara <jack@suse.cz> | 2011-05-24 15:52:40 (GMT) |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2011-05-24 15:52:40 (GMT) |
commit | 81be12c8179c1c397d3f179cdd9b3f7146cf47f1 (patch) | |
tree | b535687e88af17fc6b25329decf28563ed519395 /mm/sparse.c | |
parent | b221349fa8b45d13c3650089f0514df7d1eb36c3 (diff) | |
download | linux-81be12c8179c1c397d3f179cdd9b3f7146cf47f1.tar.xz |
jbd2: fix sending of data flush on journal commit
In data=ordered mode, it's theoretically possible (however rare) that
an inode is filed to transaction's t_inode_list and a flusher thread
writes all the data and inode is reclaimed before the transaction
starts to commit. In such a case, we could erroneously omit sending a
flush to file system device when it is different from the journal
device (because data can still be in disk cache only).
Fix the problem by setting a flag in a transaction when some inode is added
to it and then send disk flush in the commit code when the flag is set.
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'mm/sparse.c')
0 files changed, 0 insertions, 0 deletions