aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--fs/jbd/commit.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/jbd/commit.c b/fs/jbd/commit.c
index 31853eb65b4c..8e08efcaede2 100644
--- a/fs/jbd/commit.c
+++ b/fs/jbd/commit.c
@@ -131,6 +131,8 @@ static int journal_write_commit_record(journal_t *journal,
131 barrier_done = 1; 131 barrier_done = 1;
132 } 132 }
133 ret = sync_dirty_buffer(bh); 133 ret = sync_dirty_buffer(bh);
134 if (barrier_done)
135 clear_buffer_ordered(bh);
134 /* is it possible for another commit to fail at roughly 136 /* is it possible for another commit to fail at roughly
135 * the same time as this one? If so, we don't want to 137 * the same time as this one? If so, we don't want to
136 * trust the barrier flag in the super, but instead want 138 * trust the barrier flag in the super, but instead want
@@ -148,7 +150,6 @@ static int journal_write_commit_record(journal_t *journal,
148 spin_unlock(&journal->j_state_lock); 150 spin_unlock(&journal->j_state_lock);
149 151
150 /* And try again, without the barrier */ 152 /* And try again, without the barrier */
151 clear_buffer_ordered(bh);
152 set_buffer_uptodate(bh); 153 set_buffer_uptodate(bh);
153 set_buffer_dirty(bh); 154 set_buffer_dirty(bh);
154 ret = sync_dirty_buffer(bh); 155 ret = sync_dirty_buffer(bh);