Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp2711410pxv; Sun, 11 Jul 2021 23:29:48 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx45hBMZOSH5sBLpVH8upvhuyv4PhjzxFeN88st+SxQzSaV+tQcab45zt4CzpzSnpVhQxEx X-Received: by 2002:a17:906:b201:: with SMTP id p1mr50463005ejz.30.1626071388429; Sun, 11 Jul 2021 23:29:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626071388; cv=none; d=google.com; s=arc-20160816; b=sL+0GWpVY45ARYaeaFqLyZuvaBjEsCjnWYA9lGiXVMLQwOizvYTP4BwViFaQukbHpE CiMaM4fLgpa1SJUld54SKiGMWyQvYbrLw4TUplQSfhyr7xtHSAzp1dj5DoUYM9IceYPr kdO9HL6RnCIyNKOslhkP9e+ag/DbgkgzvavQ5CV/LQUFj39EgLGYVWvQuAeLfGlzfXhp +dPBMZTf2REMMcspCjjC5CdPh1mcZyoQFvOfJNIa9fEKKcssjgtRyTt9RBRZzfswSG7U o0jZM+vPDKKN/3j2Q5Gkb6llLB4T/IQMvTRCVPGogPo5KGJZEp7xLTDbmC5ASAWxja9q kXjA== 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=77JfdggkUF9eYH5z40dxyrWXq8NqqNFSHd+2YLRuYU8=; b=AVwZx/Wtn8sS1T6mufoxtlTNCoJoulBEiLPt/Uh757L3+nAb2M+pDYCy7491bQle6a aogC7fj9k15mbpNXgqD621EkLD9z+WGwRoYvw72lRfDsoE8TAqJQXsTz1q2H4mCbXV6h /NrP+2djbvtpT6oevXoPIUs4hmQaiDtuuGpDo3BZm+mNVQtsbPZ5irHJzBvRGUMSsAuz WyRP9JU2atfe9vdFx7jYqkeOr3ewlU1980C1ujSQriN7MN/dZsCohN9FY8MoD/Xug3Do 6ZCiYskSzX0m0AJ52EyBlRoEh8c9wN8laEOIPwMvCUyMaNxr8j28zcaAsljUN+siOs9E IEIA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="AIF/AKCH"; 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 nb19si18040062ejc.673.2021.07.11.23.29.25; Sun, 11 Jul 2021 23:29:48 -0700 (PDT) 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="AIF/AKCH"; 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 S236152AbhGLG3r (ORCPT + 99 others); Mon, 12 Jul 2021 02:29:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:45560 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235050AbhGLGZW (ORCPT ); Mon, 12 Jul 2021 02:25:22 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6C4E361130; Mon, 12 Jul 2021 06:22:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626070954; bh=kZcZbSICOodmW+tw82VmlXzK9HEDFbTXPZk8P/dXstc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=AIF/AKCHMBytqSTjTJzTVzsr8ZwGRW0IsdQ7mFVEfxJr8EmUIU4hH7rwBtNOo87Cx ElI+DUyth5C2IJQm4F2LcJ1/pVRsEqltLapGV9KAI7q3M39981WE3mm5rMziE4MDp3 9pwqqWh434Hg51bwQ2GsREO3tH3fmPc/XEvA6H8U= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Qu Wenruo , Anand Jain , David Sterba , Sasha Levin Subject: [PATCH 5.4 169/348] btrfs: clear log tree recovering status if starting transaction fails Date: Mon, 12 Jul 2021 08:09:13 +0200 Message-Id: <20210712060723.298346730@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210712060659.886176320@linuxfoundation.org> References: <20210712060659.886176320@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: David Sterba [ Upstream commit 1aeb6b563aea18cd55c73cf666d1d3245a00f08c ] When a log recovery is in progress, lots of operations have to take that into account, so we keep this status per tree during the operation. Long time ago error handling revamp patch 79787eaab461 ("btrfs: replace many BUG_ONs with proper error handling") removed clearing of the status in an error branch. Add it back as was intended in e02119d5a7b4 ("Btrfs: Add a write ahead tree log to optimize synchronous operations"). There are probably no visible effects, log replay is done only during mount and if it fails all structures are cleared so the stale status won't be kept. Fixes: 79787eaab461 ("btrfs: replace many BUG_ONs with proper error handling") Reviewed-by: Qu Wenruo Reviewed-by: Anand Jain Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/tree-log.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c index 4ff381c23cef..afc6731bb692 100644 --- a/fs/btrfs/tree-log.c +++ b/fs/btrfs/tree-log.c @@ -6327,6 +6327,7 @@ next: error: if (wc.trans) btrfs_end_transaction(wc.trans); + clear_bit(BTRFS_FS_LOG_RECOVERING, &fs_info->flags); btrfs_free_path(path); return ret; } -- 2.30.2