diff options
author | 2019-07-02 15:50:08 -0400 | |
---|---|---|
committer | 2019-07-02 15:50:08 -0400 | |
commit | 54fa16ee532705985e6c946da455856f18f63ee1 (patch) | |
tree | 5b019c4a77c281bb68e6d35f658e88b322c53beb /.gitignore | |
parent | dm verity: use message limit for data block corruption message (diff) | |
download | linux-54fa16ee532705985e6c946da455856f18f63ee1.tar.gz linux-54fa16ee532705985e6c946da455856f18f63ee1.tar.bz2 linux-54fa16ee532705985e6c946da455856f18f63ee1.zip |
dm thin metadata: check if in fail_io mode when setting needs_check
Check if in fail_io mode at start of dm_pool_metadata_set_needs_check().
Otherwise dm_pool_metadata_set_needs_check()'s superblock_lock() can
crash in dm_bm_write_lock() while accessing the block manager object
that was previously destroyed as part of a failed
dm_pool_abort_metadata() that ultimately set fail_io to begin with.
Also, update DMERR() message to more accurately describe
superblock_lock() failure.
Cc: stable@vger.kernel.org
Reported-by: Zdenek Kabelac <zkabelac@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions