From: "Darrick J. Wong" <djwong@kernel.org>
To: Pavel Reichl <preichl@redhat.com>
Cc: fstests@vger.kernel.org, shreeya.patel@collabora.com
Subject: Re: [PATCH 1/1] generic/453: Do NOT run for FSs restricting names
Date: Wed, 7 Jul 2021 07:51:58 -0700 [thread overview]
Message-ID: <20210707145158.GC11571@locust> (raw)
In-Reply-To: <20210707102007.66774-2-preichl@redhat.com>
On Wed, Jul 07, 2021 at 12:20:07PM +0200, Pavel Reichl wrote:
> Running generic/453 test is probably only useful for filesystems that
> allow unrestricted byte streams for names.
>
> Signed-off-by: Pavel Reichl <preichl@redhat.com>
> Suggested-by: Darrick J. Wong <djwong@kernel.org>
> ---
> common/rc | 11 +++++++++++
> tests/generic/453 | 1 +
> 2 files changed, 12 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index d4ad421e..7a352445 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -4599,6 +4599,17 @@ _require_od_endian_flag()
> _notrun "od does not support endian flag"
> }
>
> +_require_names_are_bytes() {
This helper needs a short description.
# Skip this test unless the filesystem treats names (directory entries,
# fs labels, and extended attribute names) as raw byte sequences.
> + case "$FSTYP" in
> + ext2|ext3|ext4|xfs|btrfs)
Does this need to _notrun ext4 filesystems that have casefolding
enabled? (Or: should we let the ext4 developers figure that out?)
> + # do nothing
> + ;;
> + *)
> + _notrun "$FSTYP does now allow unrestricted byte streams for names"
> + ;;
> + esac
> +}
> +
> init_rc
>
> ################################################################################
> diff --git a/tests/generic/453 b/tests/generic/453
> index 55ddcc01..a0fb802e 100755
> --- a/tests/generic/453
> +++ b/tests/generic/453
> @@ -15,6 +15,7 @@ _begin_fstest auto quick dir
> # Import common functions.
>
> _require_scratch
> +_require_names_are_bytes
Do you need this for generic/454 as well?
--D
>
> echo "Format and mount"
> _scratch_mkfs > $seqres.full 2>&1
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-07-07 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 10:20 [PATCH 0/1]: generic/453: Do NOT run for FSs restricting names Pavel Reichl
2021-07-07 10:20 ` [PATCH 1/1] " Pavel Reichl
2021-07-07 14:51 ` Darrick J. Wong [this message]
2021-07-07 22:40 ` Theodore Ts'o
2021-07-08 6:16 ` Pavel Reichl
2021-07-07 17:34 ` Theodore Ts'o
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=20210707145158.GC11571@locust \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=preichl@redhat.com \
--cc=shreeya.patel@collabora.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