Searched hist:a78bb11d7acd525623c6a0c2ff4e213d527573fa (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/fs/jbd2/ |
H A D | commit.c | diff a78bb11d7acd525623c6a0c2ff4e213d527573fa Tue Mar 13 14:43:04 CDT 2012 Jan Kara <jack@suse.cz> 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>
|
H A D | journal.c | diff a78bb11d7acd525623c6a0c2ff4e213d527573fa Tue Mar 13 14:43:04 CDT 2012 Jan Kara <jack@suse.cz> 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>
|