diff options
| author | Gu JinXiang <gujx@cn.fujitsu.com> | 2017-10-19 09:49:27 +0800 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2017-11-01 20:45:36 +0100 |
| commit | d28e649a5c58b779b303c252c66ee84a0f2c3b32 (patch) | |
| tree | 4e555d032e11bdb272ce1c5ed4117e78d0fad052 /fs/freevxfs | |
| parent | 19562430c6213925faba3baa9e8cb224ddd47ee6 (diff) | |
| download | op-kernel-dev-d28e649a5c58b779b303c252c66ee84a0f2c3b32.zip op-kernel-dev-d28e649a5c58b779b303c252c66ee84a0f2c3b32.tar.gz | |
btrfs: Fix bug for misused dev_t when lookup in dev state hash table.
Fix bug of commit 74d46992e0d9 ("block: replace bi_bdev with a gendisk
pointer and partitions index").
bio_dev(bio) is used to find the dev state in function
__btrfsic_submit_bio. But when dev_state is added to the hashtable, it
is using dev_t of block_device.
bio_dev(bio) returns a dev_t of part0 which is different from dev_t in
block_device(bd_dev). bd_dev in block_device represents the exact
partition.
block_device.bd_dev =
bio->bi_partno (same as block_device.bd_partno) + bio_dev(bio).
When adding a dev_state into hashtable, we use the exact partition dev_t.
So when looking it up, it should also use the exact partition dev_t.
Reproducer of this bug:
Use MOUNT_OPTIONS="-o check_int" and run btrfs/001 in fstests.
Then there will be WARNING like below.
WARNING:
btrfs: attempt to write superblock which references block M @29523968 (sda7 /1111654400/2) which is never written!
Signed-off-by: Gu JinXiang <gujx@cn.fujitsu.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/freevxfs')
0 files changed, 0 insertions, 0 deletions
