Now we move more into the locking of the transaction_t fields.

t_nr_buffers locking is just an audit-and-commentary job.


 25-akpm/fs/jbd/transaction.c |    4 +---
 1 files changed, 1 insertion(+), 3 deletions(-)

diff -puN fs/jbd/transaction.c~jbd-110-t_nr_buffers-locking fs/jbd/transaction.c
--- 25/fs/jbd/transaction.c~jbd-110-t_nr_buffers-locking	Thu Jun  5 15:14:22 2003
+++ 25-akpm/fs/jbd/transaction.c	Thu Jun  5 15:14:22 2003
@@ -1463,9 +1463,7 @@ __blist_del_buffer(struct journal_head *
  * is holding onto a copy of one of thee pointers, it could go bad.
  * Generally the caller needs to re-read the pointer from the transaction_t.
  *
- * If bh->b_jlist is BJ_SyncData then we may have been called
- * via journal_try_to_free_buffer() or journal_clean_data_list().  In that
- * case, j_list_lock will be held, and the journal may not be locked.
+ * Called under j_list_lock.  The journal may not be locked.
  */
 void __journal_unfile_buffer(struct journal_head *jh)
 {

_