summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorMike Snitzer <snitzer@redhat.com>2019-07-02 15:50:08 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-09-16 08:22:21 +0200
commitecf99cdea02dcc792c27a52d1cf3e1c532551479 (patch)
treec87006a9ea24316b10607ec034bb182d10440894 /Documentation
parent5e9a2ce6d3b4a50a0abf754505e5a5ca32bccde5 (diff)
downloadlinux-stable-ecf99cdea02dcc792c27a52d1cf3e1c532551479.tar.gz
linux-stable-ecf99cdea02dcc792c27a52d1cf3e1c532551479.tar.bz2
linux-stable-ecf99cdea02dcc792c27a52d1cf3e1c532551479.zip
dm thin metadata: check if in fail_io mode when setting needs_check
[ Upstream commit 54fa16ee532705985e6c946da455856f18f63ee1 ] 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> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions