Theodore Ts'o e447183180 jbd2: call __jbd2_log_start_commit with j_state_lock write locked ... On an SMP ARM system running ext4, I've received a report that the first J_ASSERT in jbd2_journal_commit_transaction has been triggering: J_ASSERT(journal->j_running_transaction != NULL); While investigating possible causes for this problem, I noticed that __jbd2_log_start_commit() is getting called with j_state_lock only read-locked, in spite of the fact that it's possible for it might j_commit_request. Fix this by grabbing the necessary information so we can test to see if we need to start a new transaction before dropping the read lock, and then calling jbd2_log_start_commit() which will grab the write lock. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>		2011-02-12 08:18:24 -05:00
..
checkpoint.c	Merge branch 'next' into upstream-merge	2010-10-27 23:44:47 -04:00
commit.c	Merge branch 'next' into upstream-merge	2010-10-27 23:44:47 -04:00
journal.c	jbd2: call __jbd2_log_start_commit with j_state_lock write locked	2011-02-12 08:18:24 -05:00
Kconfig
Makefile
recovery.c	jbd2: move debug message into debug #ifdef	2010-12-18 13:36:33 -05:00
revoke.c
transaction.c	jbd2: call __jbd2_log_start_commit with j_state_lock write locked	2011-02-12 08:18:24 -05:00