From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Marcos Paulo de Souza <marcos@mpdesouza.com>,
linux-btrfs@vger.kernel.org, dsterba@suse.com
Cc: Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: Re: [PATCH] progs: tests: Avoid multidevice test on 32bit platforms
Date: Mon, 24 Feb 2020 13:52:00 +0800 [thread overview]
Message-ID: <9115debc-12e5-4de0-d3ae-d71b103ebffa@gmx.com> (raw)
In-Reply-To: <20200215232819.30280-1-marcos@mpdesouza.com>
[-- Attachment #1.1: Type: text/plain, Size: 2148 bytes --]
On 2020/2/16 上午7:28, Marcos Paulo de Souza wrote:
> From: Marcos Paulo de Souza <mpdesouza@suse.com>
>
> This test uses truncate utility to create a 6E file but this fails
> currently fails for PPC32[1], but it will also fail to other 32bit
> platforms, so skip this test in these platforms.
>
> [1]: https://github.com/kdave/btrfs-progs/issues/192
>
> Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com>
> ---
>
> I couldn't find a way to make truncate to use O_LARGEFILE option. I though even
> to write a helper to open the file using this flag and later on call ftruncate,
> but isn't it one more helper to maintain?
>
> If there are better ideas to avoid skipping this test, please let me know!
What about testing the first 6E file allocation?
If the first failed, then it means the system can't handle, and we skip
the test.
Skipping the whole 32bit systems looks overkilled to me.
Thanks,
Qu
>
> tests/common | 15 +++++++++++++++
> tests/mkfs-tests/018-multidevice-overflow/test.sh | 1 +
> 2 files changed, 16 insertions(+)
>
> diff --git a/tests/common b/tests/common
> index 605cf72c..9aa69a1a 100644
> --- a/tests/common
> +++ b/tests/common
> @@ -580,6 +580,21 @@ check_min_kernel_version()
> return 0
> }
>
> +check_32bit_machine()
> +{
> + local msg
> +
> + msg="$1"
> + if [ -z "$msg" ]; then
> + msg="Skipping test on 32bit machines"
> + fi
> +
> + long_bit=$(getconf LONG_BIT)
> + if [ $long_bit -eq 32 ]; then
> + _not_run "$msg"
> + fi
> +}
> +
> # how many files to create.
> DATASET_SIZE=50
>
> diff --git a/tests/mkfs-tests/018-multidevice-overflow/test.sh b/tests/mkfs-tests/018-multidevice-overflow/test.sh
> index 6c2f4dba..8bb3d5a9 100755
> --- a/tests/mkfs-tests/018-multidevice-overflow/test.sh
> +++ b/tests/mkfs-tests/018-multidevice-overflow/test.sh
> @@ -5,6 +5,7 @@ source "$TEST_TOP/common"
>
> check_prereq mkfs.btrfs
> check_prereq btrfs
> +check_32bit_machine "32bit machines can't handle 6E file sizes"
>
> setup_root_helper
> prepare_test_dev
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-02-24 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 23:28 [PATCH] progs: tests: Avoid multidevice test on 32bit platforms Marcos Paulo de Souza
2020-02-24 5:52 ` Qu Wenruo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9115debc-12e5-4de0-d3ae-d71b103ebffa@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcos@mpdesouza.com \
--cc=mpdesouza@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox