From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from szxga06-in.huawei.com ([45.249.212.32]:35506 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726335AbfBTBz7 (ORCPT ); Tue, 19 Feb 2019 20:55:59 -0500 Received: from DGGEMS413-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id D696E63FA27B1F5C8903 for ; Wed, 20 Feb 2019 09:55:57 +0800 (CST) From: Yufen Yu Subject: [PATCH 3/5] generic/351: use the common function _get_max_file_size Date: Wed, 20 Feb 2019 09:59:53 +0800 Message-ID: <20190220015955.26342-4-yuyufen@huawei.com> In-Reply-To: <20190220015955.26342-1-yuyufen@huawei.com> References: <20190220015955.26342-1-yuyufen@huawei.com> MIME-Version: 1.0 Content-Type: text/plain Sender: fstests-owner@vger.kernel.org To: fstests@vger.kernel.org List-ID: We use common function _get_max_file_size to get the max file size supported by the filesystems and let the code be clean. Signed-off-by: Yufen Yu --- tests/generic/351 | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/tests/generic/351 b/tests/generic/351 index e326dca1..5fd7c303 100755 --- a/tests/generic/351 +++ b/tests/generic/351 @@ -62,17 +62,8 @@ $XFS_IO_PROG -c "fpunch 512 512" $dev echo "Zero range past MAX_LFS_FILESIZE keep size" # zod = MAX_LFS_FILESIZE -case "$(getconf LONG_BIT)" in -"32") - zod=$(( ($(getconf PAGE_SIZE) << ($(getconf LONG_BIT) - 1) ) - 1)) - ;; -"64") - zod=9223372036854775807 - ;; -*) - _fail "sizeof(long) == $(getconf LONG_BIT)?" - ;; -esac +zod=$(_get_max_file_size) + $XFS_IO_PROG -c "fzero -k 512k $zod" $dev echo "Zero range past MAX_LFS_FILESIZE" -- 2.16.2.dirty