summaryrefslogtreecommitdiffstats
path: root/fs/jbd/commit.c
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2012-04-07 12:33:03 +0200
committerJan Kara <jack@suse.cz>2012-05-15 23:34:36 +0200
commit9754e39c7bc51328f145e933bfb0df47cd67b6e9 (patch)
treed2fa043f74939d049d6934aea6ab7b1c272be8a5 /fs/jbd/commit.c
parentf72cf5e223a28d3b3ea7dc9e40464fd534e359e8 (diff)
downloadop-kernel-dev-9754e39c7bc51328f145e933bfb0df47cd67b6e9.zip
op-kernel-dev-9754e39c7bc51328f145e933bfb0df47cd67b6e9.tar.gz
jbd: 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>
Diffstat (limited to 'fs/jbd/commit.c')
-rw-r--r--fs/jbd/commit.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/jbd/commit.c b/fs/jbd/commit.c
index 9d31e6a..dba9cfd 100644
--- a/fs/jbd/commit.c
+++ b/fs/jbd/commit.c
@@ -308,7 +308,7 @@ void journal_commit_transaction(journal_t *journal)
/* Do we need to erase the effects of a prior journal_flush? */
if (journal->j_flags & JFS_FLUSHED) {
jbd_debug(3, "super block updated\n");
- journal_update_superblock(journal, 1);
+ journal_update_sb_log_tail(journal);
} else {
jbd_debug(3, "superblock not updated\n");
}
OpenPOWER on IntegriCloud