public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
	linux-unionfs@vger.kernel.org,  linux-fsdevel@vger.kernel.org
Subject: Re: lots of fstests cases fail on overlay with util-linux 2.40.2 (new mount APIs)
Date: Mon, 28 Oct 2024 13:22:52 +0100	[thread overview]
Message-ID: <20241028-eigelb-quintessenz-2adca4670ee8@brauner> (raw)
In-Reply-To: <20241026180741.cfqm6oqp3frvasfm@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Sun, Oct 27, 2024 at 02:07:41AM +0800, Zorro Lang wrote:
> Hi,
> 
> Recently, I hit lots of fstests cases fail on overlayfs (xfs underlying, no
> specific mount options), e.g.
> 
> FSTYP         -- overlay
> PLATFORM      -- Linux/s390x s390x-xxxx 6.12.0-rc4+ #1 SMP Fri Oct 25 14:29:18 EDT 2024
> MKFS_OPTIONS  -- -m crc=1,finobt=1,rmapbt=0,reflink=1,inobtcount=1,bigtime=1 /mnt/fstests/SCRATCH_DIR
> MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0 /mnt/fstests/SCRATCH_DIR /mnt/fstests/SCRATCH_DIR/ovl-mnt
> 
> generic/294       [failed, exit status 1]- output mismatch (see /var/lib/xfstests/results//generic/294.out.bad)
>     --- tests/generic/294.out	2024-10-25 14:38:32.098692473 -0400
>     +++ /var/lib/xfstests/results//generic/294.out.bad	2024-10-25 15:02:34.698605062 -0400
>     @@ -1,5 +1,5 @@
>      QA output created by 294
>     -mknod: SCRATCH_MNT/294.test/testnode: File exists
>     -mkdir: cannot create directory 'SCRATCH_MNT/294.test/testdir': File exists
>     -touch: cannot touch 'SCRATCH_MNT/294.test/testtarget': Read-only file system
>     -ln: creating symbolic link 'SCRATCH_MNT/294.test/testlink': File exists
>     +mount: /mnt/fstests/SCRATCH_DIR/ovl-mnt: fsconfig system call failed: overlay: No changes allowed in reconfigure.
>     +       dmesg(1) may have more information after failed mount system call.

In the new mount api overlayfs has been changed to reject invalid mount
option on remount whereas in the old mount api we just igorned them.
If this a big problem then we need to change overlayfs to continue
ignoring garbage mount options passed to it during remount.

  reply	other threads:[~2024-10-28 12:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 18:07 lots of fstests cases fail on overlay with util-linux 2.40.2 (new mount APIs) Zorro Lang
2024-10-28 12:22 ` Christian Brauner [this message]
2024-10-28 19:28   ` Zorro Lang
2024-10-28 23:13     ` Dave Chinner
2024-10-29  5:44       ` Ian Kent
2024-10-29  6:13         ` Ian Kent
2024-10-30  1:23           ` Ian Kent
2024-11-04 17:03     ` Amir Goldstein
2024-10-29 13:05   ` Colin Walters
2024-10-31  3:48   ` Eric Sandeen
2024-10-31 10:29     ` Christian Brauner
2024-11-04 16:41       ` Miklos Szeredi
2024-11-11 12:30         ` Christian Brauner

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=20241028-eigelb-quintessenz-2adca4670ee8@brauner \
    --to=brauner@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=zlang@redhat.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