diff options
| author | Jan Kara <jack@suse.cz> | 2012-03-13 15:43:04 -0400 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2015-10-13 03:46:00 +0100 |
| commit | 7f63bfd0051575b4487f2e17b44e2cc4eb39384b (patch) | |
| tree | ae7ac01ff679b16e93bcf2113b3f512a06919ac7 /drivers | |
| parent | 516aa86b9ffaa8daba9dd3e8ef16350ffafbb25e (diff) | |
| download | kernel_samsung_smdk4412-7f63bfd0051575b4487f2e17b44e2cc4eb39384b.zip kernel_samsung_smdk4412-7f63bfd0051575b4487f2e17b44e2cc4eb39384b.tar.gz kernel_samsung_smdk4412-7f63bfd0051575b4487f2e17b44e2cc4eb39384b.tar.bz2 | |
jbd2: protect all log tail updates with j_checkpoint_mutex
commit a78bb11d7acd525623c6a0c2ff4e213d527573fa upstream.
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>
[bwh: Backported to 3.2:
- Adjust context
- Add unlock on the error path in jbd2_journal_flush()]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Cc: Bartosz Kwitniewski <zerg2000@astral.org.pl>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions