Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1717927rwl; Thu, 30 Mar 2023 00:04:13 -0700 (PDT) X-Google-Smtp-Source: AKy350bHuGX1SedGvN4mRCkqPIoUlBYy8Uuqaaluxmj6T/9ZQL0bp1lb7AKJghVpPmkBvQvlrWF8 X-Received: by 2002:a17:902:ec8f:b0:1a1:af34:ab35 with SMTP id x15-20020a170902ec8f00b001a1af34ab35mr28885459plg.2.1680159852911; Thu, 30 Mar 2023 00:04:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680159852; cv=none; d=google.com; s=arc-20160816; b=LtTFDlOsx47mlcAlwBS4F2fTzzL4J54PRRwkF/gNPzVMjItvXUEkES8r5DsXIboV4w pvY6nyTr/PYreqYxeZU3Pu2/IT1eVNpex2snlukVpQTjfMICV6Ch50vHTh1mBH9GJGsS IUaXzMYj0jYJ3NA72R1FbNWaqOG7MevH7CaRHVgKYrp6HIpGxTfrfkRUgHQtRUoxNrRX KXgX9TcXaIvO0gXaSKqvTQuuhy+FwutIjOQIQBGBlNFn2Ur1bWfVJTPSVKk0uctTdF5v gbz+aF7fQ+7gjNycBJmjh8eR/weHn166UrhXnQBhBiG4QhGzLWynYKe/op4St/twVK7t GwhQ== 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 :references:in-reply-to:message-id:date:subject:cc:to:from; bh=ODHP4vgwk5IL9hJoxtmf5tbqXwh88bEz5VxVebgPqmY=; b=S0KFZzioDT/PxsNiIY55EQ7xR01/2g1Qx1hM9cBf4Kig2NMrtSNZKMj8FcVSioc7ob agphF/moGs4qIuQJLf8bK4STt0TjA8qj9shPh9OnYAGzZF4DZzlpxwzdvszlQBm82arS wkRgcsy8+RhgyPqCsLyEQUo7WcmOiAPqdh0ZkZbayxLwWJVGkl1GiY2xpO3Qoz+91ibg /i5HbX8IbJmbMr7dy//4/bYlhmrQsegd9O3DDCWoXA2/WPK3aHEWUwFvxsJfdj+xa/Ep pklUrO2K+e6XSbcZVUECwbJVwDg+B3FAa6X7U77F4baoxVqHT7Dz3kPQ8N6k1fhOoSwO mOSw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ja20-20020a170902efd400b001a1cbc5c04fsi969462plb.341.2023.03.30.00.03.54; Thu, 30 Mar 2023 00:04:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229864AbjC3G5n (ORCPT + 99 others); Thu, 30 Mar 2023 02:57:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49046 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229997AbjC3G5m (ORCPT ); Thu, 30 Mar 2023 02:57:42 -0400 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7C37C469A for ; Wed, 29 Mar 2023 23:57:37 -0700 (PDT) Received: from dggpeml500016.china.huawei.com (unknown [172.30.72.56]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4PnDfZ5Y17zSqZM; Thu, 30 Mar 2023 14:53:58 +0800 (CST) Received: from huawei.com (10.175.127.227) by dggpeml500016.china.huawei.com (7.185.36.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Thu, 30 Mar 2023 14:57:35 +0800 From: zhanchengbin To: , CC: , , , , zhanchengbin Subject: [PATCH v2 2/2] e2fsck: add sync error handle to e2fsck. Date: Thu, 30 Mar 2023 14:56:56 +0800 Message-ID: <20230330065656.3275785-3-zhanchengbin1@huawei.com> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20230330065656.3275785-1-zhanchengbin1@huawei.com> References: <20230330065656.3275785-1-zhanchengbin1@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.175.127.227] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To dggpeml500016.china.huawei.com (7.185.36.70) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org If fsync fails during fsck, it is silent and users will not perceive it, so a function to handle fsync failure should be added to fsck. Signed-off-by: zhanchengbin --- e2fsck/ehandler.c | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/e2fsck/ehandler.c b/e2fsck/ehandler.c index 71ca301c..1d95a89d 100644 --- a/e2fsck/ehandler.c +++ b/e2fsck/ehandler.c @@ -118,6 +118,27 @@ static errcode_t e2fsck_handle_write_error(io_channel channel, return error; } +static errcode_t e2fsck_handle_sync_error(io_channel channel, + errcode_t error) +{ + ext2_filsys fs = (ext2_filsys) channel->app_data; + e2fsck_t ctx; + + ctx = (e2fsck_t) fs->priv_data; + if (ctx->flags & E2F_FLAG_EXITING) + return 0; + + if (operation) + printf(_("Error during fsync of dirty metadata while %s: %s "), + operation, error_message(error)); + else + printf(_("Error during fsync of dirty metadata: %s "), + error_message(error)); + preenhalt(ctx); + + return error; +} + const char *ehandler_operation(const char *op) { const char *ret = operation; @@ -130,4 +151,5 @@ void ehandler_init(io_channel channel) { channel->read_error = e2fsck_handle_read_error; channel->write_error = e2fsck_handle_write_error; + channel->sync_error = e2fsck_handle_sync_error; } -- 2.31.1