From patchwork Fri May 21 12:00:38 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Chen Long X-Patchwork-Id: 12272971 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.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,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 0EE48C43460 for ; Fri, 21 May 2021 12:00:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E3DA9613DA for ; Fri, 21 May 2021 12:00:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230081AbhEUMCF (ORCPT ); Fri, 21 May 2021 08:02:05 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:3618 "EHLO szxga05-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232810AbhEUMBe (ORCPT ); Fri, 21 May 2021 08:01:34 -0400 Received: from dggems706-chm.china.huawei.com (unknown [172.30.72.58]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4FmlSf1Pq6zQpkH; Fri, 21 May 2021 19:56:34 +0800 (CST) Received: from dggpemm500002.china.huawei.com (7.185.36.229) by dggems706-chm.china.huawei.com (10.3.19.183) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Fri, 21 May 2021 20:00:06 +0800 Received: from huawei.com (10.67.174.154) by dggpemm500002.china.huawei.com (7.185.36.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Fri, 21 May 2021 20:00:05 +0800 From: chenlong To: , , CC: Subject: [PATCH v3] ext4/048: Add new regression test Date: Fri, 21 May 2021 20:00:38 +0800 Message-ID: <20210521120038.139848-1-chenlongcl.chen@huawei.com> X-Mailer: git-send-email 2.18.0.huawei.25 MIME-Version: 1.0 X-Originating-IP: [10.67.174.154] X-ClientProxiedBy: dggems701-chm.china.huawei.com (10.3.19.178) To dggpemm500002.china.huawei.com (7.185.36.229) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: fstests@vger.kernel.org Check the block group zero and prevent initializing reserved inodes. But in some special cases, the reserved inode may not all belong to the group zero, it may exist into the second group if we format  filesystem below. mkfs.ext4 -b 4096 -g 8192 -N 1024 -I 4096 /dev/sda So, it will end up triggering a false positive report of a corrupted file system It's a regression test for commit a149d2a5cabb. Signed-off-by: Chen Long --- tests/ext4/048 | 60 ++++++++++++++++++++++++++++++++++++++++++++++ tests/ext4/048.out | 5 ++++ tests/ext4/group | 1 + 3 files changed, 66 insertions(+) create mode 100755 tests/ext4/048 create mode 100644 tests/ext4/048.out diff --git a/tests/ext4/048 b/tests/ext4/048 new file mode 100755 index 00000000..fbbd229a --- /dev/null +++ b/tests/ext4/048 @@ -0,0 +1,60 @@ +#! /bin/bash +# SPDX-License-Identifier: GPL-2.0 +# Copyright (c) 2021 Huawei. All Rights Reserved. +# +# FS QA Test 048 +# +# Regression test for commit: +# a149d2a5cabb(ext4: fix check to prevent false positive report of incorrect +# used inodes) +# +seq=`basename $0` +seqres=$RESULT_DIR/$seq +echo "QA output created by $seq" + +here=`pwd` +tmp=/tmp/$$ +status=1 # failure is the default! +trap "_cleanup; exit \$status" 0 1 2 3 15 + +_cleanup() +{ + cd / + rm -f $tmp.* +} + +# get standard environment, filters and checks +. ./common/rc +. ./common/filter + +# remove previous $seqres.full before test +rm -f $seqres.full + +# real QA test starts here +_supported_fs ext4 +_require_scratch + +# default sleep interval +sleep_time=5 + +echo "+ create scratch fs" +_scratch_mkfs_ext4 -b 4096 -g 8192 -N 1024 -I 4096 >> $seqres.full 2>&1 + +echo "+ mount fs" +_scratch_mount -o errors=remount-ro +# The default maximum wake-up delay of the lazy init thread of ext4 is +# EXT4_DEF_LI_MAX_START_DELAY (5s). +# After mounting the file system, the lazy init thread will be awakened to +# perform group initialization at 0~5s after the current time. If an error +# is detected during the initialization process, it will be set to read-only, +# so the test case needs to delay a little while waiting for the init thread +# to execute. +sleep $sleep_time + +echo "+ check mountpoint status" +cat /proc/self/mounts | grep -w ${SCRATCH_MNT} | \ + $AWK_PROG '{print $4}' | grep -oE '^rw,' | tee -a $seqres.full + +# success, all done +status=0 +exit diff --git a/tests/ext4/048.out b/tests/ext4/048.out new file mode 100644 index 00000000..16e50e86 --- /dev/null +++ b/tests/ext4/048.out @@ -0,0 +1,5 @@ +QA output created by 048 ++ create scratch fs ++ mount fs ++ check mountpoint status +rw, diff --git a/tests/ext4/group b/tests/ext4/group index ceda2ba6..82b77efb 100644 --- a/tests/ext4/group +++ b/tests/ext4/group @@ -50,6 +50,7 @@ 045 auto dir 046 auto prealloc quick 047 auto quick dax +048 auto quick 271 auto rw quick 301 aio auto ioctl rw stress defrag 302 aio auto ioctl rw stress defrag