From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-16.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CB9E9C43464 for ; Fri, 18 Sep 2020 02:24:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 883B222211 for ; Fri, 18 Sep 2020 02:24:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600395881; bh=cUvrW7T36ipANE4OrMxt9kWnwTYvgZ785NdGSLcSUOU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=lgndv/Qtz0ZOkyNeUJgbq6YTWekABdDgMNCzqQfI8Q6sUg9uT3+L/we2PML+idQno LFELSPGNOPy+lUZ1Q/0QH6WxxjzqRavrzMQXmKH7jBCQnpDCtnPOy2GDX7fvUDrKhX 9/lQIGqGTX7XuYhfpGTNfRxJp59nLUJRRDoIJzas= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729448AbgIRCYl (ORCPT ); Thu, 17 Sep 2020 22:24:41 -0400 Received: from mail.kernel.org ([198.145.29.99]:46380 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729087AbgIRCQf (ORCPT ); Thu, 17 Sep 2020 22:16:35 -0400 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2505E235F7; Fri, 18 Sep 2020 02:16:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600395388; bh=cUvrW7T36ipANE4OrMxt9kWnwTYvgZ785NdGSLcSUOU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=IuIb7xi5njSCzdVKlDGhBFTmUEQFKA6A4S4aCPOFSeMw5binZh9GEu9jggIN+EvkC 5Y8ZbpPsozaZTmXsT4Fvi7T+8liIGs448Jrh9oP89GyKScmOZ4mqb3Oip1E5G2nOnS lAFV1faGzKYE1xBxy8CwQj7q6wQ4Spwbz3DNmgKk= From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: David Sterba , Sasha Levin , linux-btrfs@vger.kernel.org Subject: [PATCH AUTOSEL 4.9 79/90] btrfs: don't force read-only after error in drop snapshot Date: Thu, 17 Sep 2020 22:14:44 -0400 Message-Id: <20200918021455.2067301-79-sashal@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20200918021455.2067301-1-sashal@kernel.org> References: <20200918021455.2067301-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org From: David Sterba [ Upstream commit 7c09c03091ac562ddca2b393e5d65c1d37da79f1 ] Deleting a subvolume on a full filesystem leads to ENOSPC followed by a forced read-only. This is not a transaction abort and the filesystem is otherwise ok, so the error should be just propagated to the callers. This is caused by unnecessary call to btrfs_handle_fs_error for all errors, except EAGAIN. This does not make sense as the standard transaction abort mechanism is in btrfs_drop_snapshot so all relevant failures are handled. Originally in commit cb1b69f4508a ("Btrfs: forced readonly when btrfs_drop_snapshot() fails") there was no return value at all, so the btrfs_std_error made some sense but once the error handling and propagation has been implemented we don't need it anymore. Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/extent-tree.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index c0033a0d00787..b5bff1e760a34 100644 --- a/fs/btrfs/extent-tree.c +++ b/fs/btrfs/extent-tree.c @@ -9435,8 +9435,6 @@ out: */ if (!for_reloc && root_dropped == false) btrfs_add_dead_root(root); - if (err && err != -EAGAIN) - btrfs_handle_fs_error(fs_info, err, NULL); return err; } -- 2.25.1