The patch titled
jbd2: need to hold j_state_lock during updates to transaction t_state
has been removed from the -mm tree. Its filename was
jbd2-need-to-hold-j_state_lock-during-updates-to-transaction-t_state.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: jbd2: need to hold j_state_lock during updates to transaction t_state
From: Mingming Cao <cmm@xxxxxxxxxx>
Updating the current transaction's t_state is protected by j_state_lock. We
need to do the same when updating t_state to T_COMMIT.
Signed-off-by: Mingming Cao <cmm@xxxxxxxxxx>
Cc: Jan Kara <jack@xxxxxx>
Cc: Theodore Ts'o <tytso@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/jbd2/commit.c | 2 ++
1 file changed, 2 insertions(+)
diff -puN fs/jbd2/commit.c~jbd2-need-to-hold-j_state_lock-during-updates-to-transaction-t_state fs/jbd2/commit.c
--- a/fs/jbd2/commit.c~jbd2-need-to-hold-j_state_lock-during-updates-to-transaction-t_state
+++ a/fs/jbd2/commit.c
@@ -563,7 +563,9 @@ void jbd2_journal_commit_transaction(jou
* transaction! Now comes the tricky part: we need to write out
* metadata. Loop over the transaction's entire buffer list:
*/
+ spin_lock(&journal->j_state_lock);
commit_transaction->t_state = T_COMMIT;
+ spin_unlock(&journal->j_state_lock);
stats.u.run.rs_logging = jiffies;
stats.u.run.rs_flushing = jbd2_time_diff(stats.u.run.rs_flushing,
_
Patches currently in -mm which might be from cmm@xxxxxxxxxx are
jbd-need-to-hold-j_state_lock-to-updates-to-transaction-t_state-to-t_commit.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
