summaryrefslogtreecommitdiff
path: root/block/blk-mq-rdma.c
diff options
context:
space:
mode:
authorQu Wenruo <wqu@suse.com>2019-12-09 18:54:35 +0800
committerDavid Sterba <dsterba@suse.com>2020-01-20 16:40:56 +0100
commit147a097cf035ef7225542605f4a61d9fab70dc84 (patch)
treeba25da2bc88b93508d6cda67a3c80e1f2b3fdfd3 /block/blk-mq-rdma.c
parent57a0e67491914f6187b1847ee3b1a01a556b9238 (diff)
btrfs: tree-checker: Verify location key for DIR_ITEM/DIR_INDEX
[PROBLEM] There is a user report in the mail list, showing the following corrupted tree blocks: item 62 key (486836 DIR_ITEM 2543451757) itemoff 6273 itemsize 74 location key (4065004 INODE_ITEM 1073741824) type FILE transid 21397 data_len 0 name_len 44 name: FILENAME Note that location key, its offset should be 0 for all INODE_ITEMS. This caused failed lookup of the inode. [CAUSE] That offending value, 1073741824, is 0x40000000. So this looks like a memory bit flip. [FIX] This patch will enhance tree-checker to check location key of DIR_INDEX/DIR_ITEM/XATTR_ITEM. There are several different combinations needs to check: - item_key.type == DIR_INDEX/DIR_ITEM * location_key.type == BTRFS_INODE_ITEM_KEY This location_key should follow the check in inode_item check. * location_key.type == BTRFS_ROOT_ITEM_KEY Despite the existing check, DIR_INDEX/DIR_ITEM can only points to subvolume trees. * All other keys are not allowed. - item_key.type == XATTR_ITEM location_key should be all 0. Reported-by: Mike Gilbert <floppymaster@gmail.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'block/blk-mq-rdma.c')
0 files changed, 0 insertions, 0 deletions