From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: generic/699 fails on ext4 due to using ext4 mount options w/ overlayfs
Date: Tue, 18 Mar 2025 19:51:16 -0400 [thread overview]
Message-ID: <20250318235116.GE787758@mit.edu> (raw)
In-Reply-To: <c46d8caf-053a-4af1-b562-7ca7203cb926@sandeen.net>
On Tue, Mar 18, 2025 at 03:39:33PM -0500, Eric Sandeen wrote:
> generic/699 fails because _overlay_mount_dirs() uses _common_dev_mount_options(),
> and when FSTYP is ext4, that yields "-o acl,user_xattr" and acl is not a valid
> option for overlayfs.
Hmm, I hadn't noticed because the test is getting skipped for me:
BEGIN TEST 4k (1 test): Ext4 4k block Tue Mar 18 19:44:51 EDT 2025
DEVICE: /dev/vdb
EXT_MKFS_OPTIONS: -b 4096
EXT_MOUNT_OPTIONS: -o block_validity
FSTYP -- ext4
PLATFORM -- Linux/x86_64 kvm-xfstests 6.14.0-rc2-xfstests-00063-g6630cf085eb0 #14 SMP PREEMPT_DYNAMIC Mon Mar 17 11:19:56 EDT 2025
MKFS_OPTIONS -- -F -q -b 4096 /dev/vdc
MOUNT_OPTIONS -- -o acl,user_xattr -o block_validity /dev/vdc /vdc
generic/699 [19:44:51][ 12.536740] run fstests generic/699 at 2025-03-18 19:44:51
[ 12.794084] overlay: Unknown parameter 'acl'
[19:44:52] [not run]
generic/699 -- overlayfs doesn't support idmappped layers
Ran: generic/699
I haven't really played with idmapped mount. Is there some CONFIG
option I need to enable this test to run?
- Ted
next prev parent reply other threads:[~2025-03-18 23:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 20:39 generic/699 fails on ext4 due to using ext4 mount options w/ overlayfs Eric Sandeen
2025-03-18 23:51 ` Theodore Ts'o [this message]
2025-03-19 0:58 ` Eric Sandeen
2025-03-19 3:58 ` Theodore Ts'o
2025-03-19 15:36 ` Eric Sandeen
2025-03-19 15:11 ` Zorro Lang
2025-03-19 15:39 ` Zorro Lang
2025-03-19 16:44 ` Theodore Ts'o
2025-03-19 16:54 ` Eric Sandeen
2025-03-19 20:01 ` Zorro Lang
2025-03-19 23:32 ` Theodore Ts'o
2025-03-20 5:25 ` Zorro Lang
2025-03-20 7:50 ` Amir Goldstein
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=20250318235116.GE787758@mit.edu \
--to=tytso@mit.edu \
--cc=fstests@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.