jbd2: don't leak modified metadata buffers on an aborted journal
authorTheodore Ts'o <tytso@mit.edu>
Sun, 5 Feb 2017 04:14:19 +0000 (23:14 -0500)
committerWilly Tarreau <w@1wt.eu>
Tue, 20 Jun 2017 06:02:35 +0000 (08:02 +0200)
commit e112666b4959b25a8552d63bc564e1059be703e8 upstream.

If the journal has been aborted, we shouldn't mark the underlying
buffer head as dirty, since that will cause the metadata block to get
modified.  And if the journal has been aborted, we shouldn't allow
this since it will almost certainly lead to a corrupted file system.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Willy Tarreau <w@1wt.eu>
fs/jbd2/transaction.c

index 21b828c713cc3399a4964699295e14105b8d4f37..54e958125c1f3fd94b4ffdc2d418d033676f90e7 100644 (file)
@@ -1655,7 +1655,9 @@ static void __jbd2_journal_temp_unlink_buffer(struct journal_head *jh)
 
        __blist_del_buffer(list, jh);
        jh->b_jlist = BJ_None;
-       if (test_clear_buffer_jbddirty(bh))
+       if (transaction && is_journal_aborted(transaction->t_journal))
+               clear_buffer_jbddirty(bh);
+       else if (test_clear_buffer_jbddirty(bh))
                mark_buffer_dirty(bh);  /* Expose it to the VM */
 }