diff options
author | Jan Kara <jack@suse.cz> | 2012-03-13 15:41:04 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2012-03-13 15:41:04 -0400 |
commit | 24bcc89c7e7c64982e6192b4952a0a92379fc341 (patch) | |
tree | 0661b6c83fa9bb681f3aa32264323ce96c264958 /fs/jbd2/commit.c | |
parent | 31d4f3a2f3c73f279ff96a7135d7202ef6833f12 (diff) |
jbd2: split updating of journal superblock and marking journal empty
There are three case of updating journal superblock. In the first case, we want
to mark journal as empty (setting s_sequence to 0), in the second case we want
to update log tail, in the third case we want to update s_errno. Split these
cases into separate functions. It makes the code slightly more straightforward
and later patches will make the distinction even more important.
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/jbd2/commit.c')
-rw-r--r-- | fs/jbd2/commit.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/jbd2/commit.c b/fs/jbd2/commit.c index 8adc5d460f56..19371a8a9015 100644 --- a/fs/jbd2/commit.c +++ b/fs/jbd2/commit.c | |||
@@ -340,7 +340,7 @@ void jbd2_journal_commit_transaction(journal_t *journal) | |||
340 | /* Do we need to erase the effects of a prior jbd2_journal_flush? */ | 340 | /* Do we need to erase the effects of a prior jbd2_journal_flush? */ |
341 | if (journal->j_flags & JBD2_FLUSHED) { | 341 | if (journal->j_flags & JBD2_FLUSHED) { |
342 | jbd_debug(3, "super block updated\n"); | 342 | jbd_debug(3, "super block updated\n"); |
343 | jbd2_journal_update_superblock(journal, 1); | 343 | jbd2_journal_update_sb_log_tail(journal); |
344 | } else { | 344 | } else { |
345 | jbd_debug(3, "superblock not updated\n"); | 345 | jbd_debug(3, "superblock not updated\n"); |
346 | } | 346 | } |