ext4: fix block validity checks for journal inodes using indirect blocks
authorTheodore Ts'o <tytso@mit.edu>
Wed, 15 May 2019 04:51:19 +0000 (00:51 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Wed, 15 May 2019 04:51:19 +0000 (00:51 -0400)
commit170417c8c7bb2cbbdd949bf5c443c0c8f24a203b
tree70dcb3c3c3fd9c9ce8414fc495f5a4f1d46c6c51
parent7fb64133360b10edcae3c6f5afffaa449668831e
ext4: fix block validity checks for journal inodes using indirect blocks

Commit 345c0dbf3a30 ("ext4: protect journal inode's blocks using
block_validity") failed to add an exception for the journal inode in
ext4_check_blockref(), which is the function used by ext4_get_branch()
for indirect blocks.  This caused attempts to read from the ext3-style
journals to fail with:

[  848.968550] EXT4-fs error (device sdb7): ext4_get_branch:171: inode #8: block 30343695: comm jbd2/sdb7-8: invalid block

Fix this by adding the missing exception check.

Fixes: 345c0dbf3a30 ("ext4: protect journal inode's blocks using block_validity")
Reported-by: Arthur Marsh <arthur.marsh@internode.on.net>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/ext4/block_validity.c