| commit | a78bb11d7acd525623c6a0c2ff4e213d527573fa | |
| author | Jan Kara <jack@suse.cz> | |
| Tue, 13 Mar 2012 19:43:04 +0000 (13 15:43 -0400) | ||
| committer | Theodore Ts'o <tytso@mit.edu> | |
| Tue, 13 Mar 2012 19:43:04 +0000 (13 15:43 -0400) | ||
| tree | 6e2e228cc51a2138046b499d6d9002f35f6d56d0 | treesnapshot (tar.gz zip) |
| parent | 24bcc89c7e7c64982e6192b4952a0a92379fc341 | commitdiff |
jbd2: protect all log tail updates with j_checkpoint_mutex
There are some log tail updates that are not protected by j_checkpoint_mutex.
Some of these are harmless because they happen during startup or shutdown but
updates in jbd2_journal_commit_transaction() and jbd2_journal_flush() can
really race with other log tail updates (e.g. someone doing
jbd2_journal_flush() with someone running jbd2_cleanup_journal_tail()). So
protect all log tail updates with j_checkpoint_mutex.
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
There are some log tail updates that are not protected by j_checkpoint_mutex.
Some of these are harmless because they happen during startup or shutdown but
updates in jbd2_journal_commit_transaction() and jbd2_journal_flush() can
really race with other log tail updates (e.g. someone doing
jbd2_journal_flush() with someone running jbd2_cleanup_journal_tail()). So
protect all log tail updates with j_checkpoint_mutex.
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
| fs/jbd2/commit.c | diffblobblamehistory | |
| fs/jbd2/journal.c | diffblobblamehistory |