| commit | 31cb1d64da4ebd214348cad9d86e663c831c45fc | |
| author | Jan Kara <jack@suse.cz> | |
| Wed, 15 May 2019 06:57:40 +0000 (15 08:57 +0200) | ||
| committer | Jens Axboe <axboe@kernel.dk> | |
| Mon, 27 May 2019 13:35:02 +0000 (27 07:35 -0600) | ||
| tree | a1ed3907812f5623c91be7beb666495741aa4a67 | treesnapshot (tar.gz zip) |
| parent | 33ec3e53e7b1869d7851e59e126bdb0fe0bd1982 | commitdiff |
block: Don't revalidate bdev of hidden gendisk
When hidden gendisk is revalidated, there's no point in revalidating
associated block device as there's none. We would thus just create new
bdev inode, report "detected capacity change from 0 to XXX" message and
evict the bdev inode again. Avoid this pointless dance and confusing
message in the kernel log.
Reviewed-by: Hannes Reinecke <hare@suse.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
When hidden gendisk is revalidated, there's no point in revalidating
associated block device as there's none. We would thus just create new
bdev inode, report "detected capacity change from 0 to XXX" message and
evict the bdev inode again. Avoid this pointless dance and confusing
message in the kernel log.
Reviewed-by: Hannes Reinecke <hare@suse.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
| fs/block_dev.c | diffblobblamehistory |