Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp524964pxb; Wed, 3 Mar 2021 08:52:43 -0800 (PST) X-Google-Smtp-Source: ABdhPJyLfkR8/QT1kTl37AOI32oc8M6kotRwxtVkVS2bdtGsd77sUrv8xmGR1haVrw8LKb2c/6+9 X-Received: by 2002:a05:6402:35d3:: with SMTP id z19mr69766edc.143.1614790363769; Wed, 03 Mar 2021 08:52:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614790363; cv=none; d=google.com; s=arc-20160816; b=CHkNJ2gMqIAWrx+oPfX+dk4LWlF83Z8Bey/q32WaUeGiIcSlL8lpV9oCR2pimoxf1p ei/0kOhwijVttSCbfpkpd1zgfLg3EEa4apCzo47wn447yw/KFDUoONUkVHYVXu8zVVSk hrWQnqBdarddlx/PWMpfmFz75g7hJDV/TRl7WSsvzIJh0Jkb2hEwHXXVjO+LLzl++O63 3FJPaQAbBbyoTmIPIFr7usj51Qb6qfMikrya6ucsL8h1dsw3iav0PY3S3DsVM3oRhx7u gEwlquj+fcPKTe8sv8jix1IYrmK3qaIkT2iPZYINOIHi0hv+uPY90iSTh8tZXz1vH9bN ENQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=BSTcoprEccKIj2SgSzRVq9MdWpDnnYk5UHsjkcxBTik=; b=GdcFYYydxV5Y7Sz6+WvDM0pZhKx3MJLM1BdHDvBRgc/fPDSXVqJoUJ12cfz9VjCyOi jkqYFOckeIyyrN/qjJuP6SGfWY5+jQ3xiop4dGxKpgZ/XeYZ+Jx1ZqpRrnRetigfMhzV aHayDRDzi2hH1gUpp9STmdxZEhfmJI84igqYmB3jZoxfu3o1e187DWiTzMs1YyZsu3i/ rLh92B/6OV7zmHpQD0mpBWUUpEPtAnbxdxgn3DXpDQlFmVZhbbmpOFqPSQAuzOQviK0Z e5hFlvMb6sybi4Bm/S5nbVRdKDGr9BsihBgcc0IK3CuQGMXCG5PSIYsftKOQn3kJDaM6 ckBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=E0mMO6SF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t18si406163ejy.531.2021.03.03.08.52.01; Wed, 03 Mar 2021 08:52:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=E0mMO6SF; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348037AbhCBA2R (ORCPT + 99 others); Mon, 1 Mar 2021 19:28:17 -0500 Received: from mail.kernel.org ([198.145.29.99]:44648 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240058AbhCAS2f (ORCPT ); Mon, 1 Mar 2021 13:28:35 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id B676364F6A; Mon, 1 Mar 2021 17:01:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1614618070; bh=X2u5rAsk7PheiGIxhItqEsP+MbIQYGlUkD93idGX95s=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=E0mMO6SFFsFih2f9BEJJEXzRPZ0y8oMKmfOPscmwAqroVi6fSmj/oGi/0j0IeHgHA 9oBpt+rSO76L1pXAM5wvWrM2+rwwPNgRgohEEHJU8Q9mMYvUTHUxWxlcwlVpTD7RSm m3UeTlJoNcfx2V3d3kb52h+Uy1H19k8Egv/oeJik= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Josef Bacik , David Sterba Subject: [PATCH 5.4 266/340] btrfs: fix reloc root leak with 0 ref reloc roots on recovery Date: Mon, 1 Mar 2021 17:13:30 +0100 Message-Id: <20210301161101.379755777@linuxfoundation.org> X-Mailer: git-send-email 2.30.1 In-Reply-To: <20210301161048.294656001@linuxfoundation.org> References: <20210301161048.294656001@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Josef Bacik commit c78a10aebb275c38d0cfccae129a803fe622e305 upstream. When recovering a relocation, if we run into a reloc root that has 0 refs we simply add it to the reloc_control->reloc_roots list, and then clean it up later. The problem with this is __del_reloc_root() doesn't do anything if the root isn't in the radix tree, which in this case it won't be because we never call __add_reloc_root() on the reloc_root. This exit condition simply isn't correct really. During normal operation we can remove ourselves from the rb tree and then we're meant to clean up later at merge_reloc_roots() time, and this happens correctly. During recovery we're depending on free_reloc_roots() to drop our references, but we're short-circuiting. Fix this by continuing to check if we're on the list and dropping ourselves from the reloc_control root list and dropping our reference appropriately. Change the corresponding BUG_ON() to an ASSERT() that does the correct thing if we aren't in the rb tree. CC: stable@vger.kernel.org # 4.4+ Signed-off-by: Josef Bacik Reviewed-by: David Sterba Signed-off-by: David Sterba Signed-off-by: Greg Kroah-Hartman --- fs/btrfs/relocation.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) --- a/fs/btrfs/relocation.c +++ b/fs/btrfs/relocation.c @@ -1336,9 +1336,7 @@ static void __del_reloc_root(struct btrf RB_CLEAR_NODE(&node->rb_node); } spin_unlock(&rc->reloc_root_tree.lock); - if (!node) - return; - BUG_ON((struct btrfs_root *)node->data != root); + ASSERT(!node || (struct btrfs_root *)node->data == root); } spin_lock(&fs_info->trans_lock);