Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3788981pxv; Mon, 19 Jul 2021 08:47:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwc5oQIHQM56hnRjOuAMSqTV2kcaMPuEoXR8npHGwkHqvvK/HDcY2K8M2O5Qm5AALJif8CO X-Received: by 2002:a02:628b:: with SMTP id d133mr22403189jac.27.1626709621685; Mon, 19 Jul 2021 08:47:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626709621; cv=none; d=google.com; s=arc-20160816; b=dg17W1st4tP+uJ7+7aw6fW6nYPpxQ6ZhKJVfyqohq98D4ve7LRpGePwVZgjKJoG8LO us42YZi4sUsgFMpfNcKRbzPSjoTB+ssrejaOUajVgf3IFihlsB9eQrMM8JT9uHmjgfcx LCGmKoDLKl1y0+Q7kh7+6jKrHWiKjF2/qesgknwikzJx46w16liIo18HpVSZnNKgVc4c /Y4RGgkzrxg3o3nP0tb6DFxZIO6F2rVKn+3+0LE2DT8UQwzUuVNxK6V51KR3KSQs/TeW HVkn5BQKkvgHUxvBysPDTSBdMn69Z7m7buW/4+HolN6q4FwHGwDOr2QCgJTBRMTpajiz 2jRg== 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=O0oVzQxsjGiSTEMSnfQe27SHRvNOWjGLZJDzrP0u2hA=; b=zJgeicJfkuPGgVIQBeJRgxZaF7DFMe8kbh/eFUQF+Is/N1OCU+JFNOn32B2oIHThVV vQOuWjsGq0JG3Q/usUzUiDXyy3Phd/uIDa1kJI3R+OBAfR18xius1FLtscGfNf2oA+MX h4x97F6ULPFMTrKaVn+3EllsIaNE3pywZmGv7d056fiEgei4snhC8pPUjC2MhiS0wlX4 AvwvwGwha9QJMsCsBnKDUiVMnXhDNz/BNCRZr2oBhMK2ySa0iZeU1Z+afjJDtygqi+QW kic1TTLvApTFlF9HJnMxt8A7701rNxqmPLFk7GCVE5d0AG6zahqYHq2PJN97JHDGn/FC CosA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=RvL8dzUg; 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 w4si24107753iov.14.2021.07.19.08.46.49; Mon, 19 Jul 2021 08:47:01 -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=RvL8dzUg; 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 S245308AbhGSPDh (ORCPT + 99 others); Mon, 19 Jul 2021 11:03:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:53816 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245305AbhGSOiO (ORCPT ); Mon, 19 Jul 2021 10:38:14 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id D199061248; Mon, 19 Jul 2021 15:17:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626707875; bh=SgxVTqg3TOEmf5WCKocn+ohWTqbmvn+yxTfwJ7zmAnQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=RvL8dzUgRq4EsGzNKUAY4zg4RVfEFddNLsPdiIQ6uMoyc9Zje4V/oBshXJwuStJGT XcBrzBh6QLIIX+E8m/kCKvSQH7Wsl5g+12B37NcIrBLM7KyrL1+yBpFjXIYUTTdt4Y c0dIdsGGfnuoOTE0Qj7NS3tMUQ3Ud9z+N23Bvtoc= 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 4.14 091/315] btrfs: clear log tree recovering status if starting transaction fails Date: Mon, 19 Jul 2021 16:49:40 +0200 Message-Id: <20210719144945.868251942@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210719144942.861561397@linuxfoundation.org> References: <20210719144942.861561397@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 f890fdb59915..fbcfee38583b 100644 --- a/fs/btrfs/tree-log.c +++ b/fs/btrfs/tree-log.c @@ -5957,6 +5957,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