summaryrefslogtreecommitdiff
path: root/fs/minix
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2014-06-15 23:46:28 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-07-09 11:14:01 -0700
commitead37447d6eda0cb1104c8262c2b595164ccfe4b (patch)
treea6f3a39016e89b7a306f0b75283536a7a21582a3 /fs/minix
parent780ae119ce653644a8ecbcb9a98cfbfc68f2e46b (diff)
ext4: Fix buffer double free in ext4_alloc_branch()
commit c5c7b8ddfbf8cb3b2291e515a34ab1b8982f5a2d upstream. Error recovery in ext4_alloc_branch() calls ext4_forget() even for buffer corresponding to indirect block it did not allocate. This leads to brelse() being called twice for that buffer (once from ext4_forget() and once from cleanup in ext4_ind_map_blocks()) leading to buffer use count misaccounting. Eventually (but often much later because there are other users of the buffer) we will see messages like: VFS: brelse: Trying to free free buffer Another manifestation of this problem is an error: JBD2 unexpected failure: jbd2_journal_revoke: !buffer_revoked(bh); inconsistent data on disk The fix is easy - don't forget buffer we did not allocate. Also add an explanatory comment because the indexing at ext4_alloc_branch() is somewhat subtle. Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/minix')
0 files changed, 0 insertions, 0 deletions