ext4: Use bforget() in no journal mode for ext4_journal_{forget,revoke}()
authorTheodore Ts'o <tytso@mit.edu>
Thu, 10 Sep 2009 01:32:41 +0000 (21:32 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Thu, 10 Sep 2009 01:32:41 +0000 (21:32 -0400)
When ext4 is using a journal, a metadata block which is deallocated
must be passed into the journal layer so it can be dropped from the
current transaction and/or revoked.  This is done by calling the
functions ext4_journal_forget() and ext4_journal_revoke(), which call
jbd2_journal_forget(), and jbd2_journal_revoke(), respectively.

Since the jbd2_journal_forget() and jbd2_journal_revoke() call
bforget(), if ext4 is not using a journal, ext4_journal_forget() and
ext4_journal_revoke() must call bforget() to avoid a dirty metadata
block overwriting a block after it has been reallocated and reused for
another inode's data block.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
fs/ext4/ext4_jbd2.c

index eb27fd0f2ee86dd4c8badd2ed146f2a306e1f35f..ecb9ca455fd5d901a2cce418858eae2310c66fe5 100644 (file)
@@ -44,7 +44,7 @@ int __ext4_journal_forget(const char *where, handle_t *handle,
                                                  handle, err);
        }
        else
-               brelse(bh);
+               bforget(bh);
        return err;
 }
 
@@ -60,7 +60,7 @@ int __ext4_journal_revoke(const char *where, handle_t *handle,
                                                  handle, err);
        }
        else
-               brelse(bh);
+               bforget(bh);
        return err;
 }