From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CAF23189A36; Fri, 29 Mar 2024 12:42:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711716146; cv=none; b=cOYyZgjkLfwIFt+fQDWcXXiUb85cqAvolZcsAgP06ay5otfxl91G2sv4OxCeXFbkm9VpwYw1WhQWBJRWP38MfvgTY1EnEdeCkEseQzAODCJR7XZut71oHitTNaeDIEeQFEKPOVVbQp6aiAWGkjcOHdpzgZFA1NBuJh36kvjrO8w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711716146; c=relaxed/simple; bh=1LkM0DVVSxHRFqCqUyibA4ChmpR37hD2y9C2DhaWz7A=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=HZdneCl1Ewr7JOxNVK83+IWBlHDH3aWmbb9ZgpmVpfg8vmEK9Vb73Z9FRY1fzSrFsw4hk5t1+6hiYF76SBUF2f2DqoU5EWuQu0DZvMNjK+nrl4nPSPulGAcR/vCvQYhS7vBYAFmdLS09yCJxTQQ9gj2KsRbukS2Epg2OCb9hQa8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=O08lhoOF; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="O08lhoOF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6742EC43399; Fri, 29 Mar 2024 12:42:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1711716146; bh=1LkM0DVVSxHRFqCqUyibA4ChmpR37hD2y9C2DhaWz7A=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=O08lhoOF1XFiorhLYkHXS7DME+Q/DyB4zuCjjnWiUoGmsAepTx2us3b77wXfDD31C djLHhCMdjSOyeJFbqnnX430scPWbmDS3JesPmqoUQW/gfK63GTLukUCOoWrwNJPc66 KmpVQXsNoAGrKbBE2c77AF1n6+Yo0v01RQGL20e86H+1xhQauciqaRIQ1Knmm6EZSL pO+Rx13uaNZdDtIlaLDAs0I4WnGyC71nq5SkiUenWrhMmzEMh3rge2zZQKeXPtmN2d PnSii0tlX80WAPoFqiYHuGGxsUTL7g6tRSDfFR4bLTqPMJEraamOGeWztS4ZpV2R+O Okc6rBBSuohZQ== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: David Sterba , Josef Bacik , Anand Jain , Sasha Levin , clm@fb.com, linux-btrfs@vger.kernel.org Subject: [PATCH AUTOSEL 6.8 81/98] btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() Date: Fri, 29 Mar 2024 08:37:52 -0400 Message-ID: <20240329123919.3087149-81-sashal@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240329123919.3087149-1-sashal@kernel.org> References: <20240329123919.3087149-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.8.2 Content-Transfer-Encoding: 8bit From: David Sterba [ Upstream commit 7411055db5ce64f836aaffd422396af0075fdc99 ] The unhandled case in btrfs_relocate_sys_chunks() loop is a corruption, as it could be caused only by two impossible conditions: - at first the search key is set up to look for a chunk tree item, with offset -1, this is an inexact search and the key->offset will contain the correct offset upon a successful search, a valid chunk tree item cannot have an offset -1 - after first successful search, the found_key corresponds to a chunk item, the offset is decremented by 1 before the next loop, it's impossible to find a chunk item there due to alignment and size constraints Reviewed-by: Josef Bacik Reviewed-by: Anand Jain Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/volumes.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index d67785be2c778..6aae92e4b4240 100644 --- a/fs/btrfs/volumes.c +++ b/fs/btrfs/volumes.c @@ -3393,7 +3393,17 @@ static int btrfs_relocate_sys_chunks(struct btrfs_fs_info *fs_info) mutex_unlock(&fs_info->reclaim_bgs_lock); goto error; } - BUG_ON(ret == 0); /* Corruption */ + if (ret == 0) { + /* + * On the first search we would find chunk tree with + * offset -1, which is not possible. On subsequent + * loops this would find an existing item on an invalid + * offset (one less than the previous one, wrong + * alignment and size). + */ + ret = -EUCLEAN; + goto error; + } ret = btrfs_previous_item(chunk_root, path, key.objectid, key.type); -- 2.43.0