diff options
author | Jan Kara <jack@suse.cz> | 2011-05-24 12:00:54 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2011-05-24 12:00:54 -0400 |
commit | 93628ffb9ba67c154849ac6c387f98f5e3198b84 (patch) | |
tree | 5aeeedb16744a901f945897fda4822e3b852cec5 /fs/ext4/fsync.c | |
parent | bbd2be36910728f485ac78ea36e0f4f5a38e691e (diff) |
ext4: fix waiting and sending of a barrier in ext4_sync_file()
jbd2_log_start_commit() returns 1 only when we really start a
transaction. But we also need to wait for a transaction when the
commit is already running. Fix this problem by waiting for
transaction commit unconditionally (which is just a quick check if the
transaction is already committed).
Also we have to be more careful with sending of a barrier because when
transaction is being committed in parallel to ext4_sync_file()
running, we cannot be sure that the barrier the journalling code sends
happens after we wrote all the data for fsync (note that not every
data writeout needs to trigger metadata changes thus commit of some
metadata changes can be running while other data is still written
out). So use jbd2_will_send_data_barrier() helper to detect the common
cases when we can be sure barrier will be issued by the commit code
and issue the barrier ourselves in the remaining cases.
Reported-by: Edward Goggin <egoggin@vmware.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/ext4/fsync.c')
-rw-r--r-- | fs/ext4/fsync.c | 23 |
1 files changed, 7 insertions, 16 deletions
diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c index 60fe5721fbe3..ce66d2fe826c 100644 --- a/fs/ext4/fsync.c +++ b/fs/ext4/fsync.c | |||
@@ -172,6 +172,7 @@ int ext4_sync_file(struct file *file, int datasync) | |||
172 | journal_t *journal = EXT4_SB(inode->i_sb)->s_journal; | 172 | journal_t *journal = EXT4_SB(inode->i_sb)->s_journal; |
173 | int ret; | 173 | int ret; |
174 | tid_t commit_tid; | 174 | tid_t commit_tid; |
175 | bool needs_barrier = false; | ||
175 | 176 | ||
176 | J_ASSERT(ext4_journal_current_handle() == NULL); | 177 | J_ASSERT(ext4_journal_current_handle() == NULL); |
177 | 178 | ||
@@ -211,22 +212,12 @@ int ext4_sync_file(struct file *file, int datasync) | |||
211 | } | 212 | } |
212 | 213 | ||
213 | commit_tid = datasync ? ei->i_datasync_tid : ei->i_sync_tid; | 214 | commit_tid = datasync ? ei->i_datasync_tid : ei->i_sync_tid; |
214 | if (jbd2_log_start_commit(journal, commit_tid)) { | 215 | if (journal->j_flags & JBD2_BARRIER && |
215 | /* | 216 | !jbd2_trans_will_send_data_barrier(journal, commit_tid)) |
216 | * When the journal is on a different device than the | 217 | needs_barrier = true; |
217 | * fs data disk, we need to issue the barrier in | 218 | jbd2_log_start_commit(journal, commit_tid); |
218 | * writeback mode. (In ordered mode, the jbd2 layer | 219 | ret = jbd2_log_wait_commit(journal, commit_tid); |
219 | * will take care of issuing the barrier. In | 220 | if (needs_barrier) |
220 | * data=journal, all of the data blocks are written to | ||
221 | * the journal device.) | ||
222 | */ | ||
223 | if (ext4_should_writeback_data(inode) && | ||
224 | (journal->j_fs_dev != journal->j_dev) && | ||
225 | (journal->j_flags & JBD2_BARRIER)) | ||
226 | blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL, | ||
227 | NULL); | ||
228 | ret = jbd2_log_wait_commit(journal, commit_tid); | ||
229 | } else if (journal->j_flags & JBD2_BARRIER) | ||
230 | blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL, NULL); | 221 | blkdev_issue_flush(inode->i_sb->s_bdev, GFP_KERNEL, NULL); |
231 | out: | 222 | out: |
232 | trace_ext4_sync_file_exit(inode, ret); | 223 | trace_ext4_sync_file_exit(inode, ret); |