From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
"fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: generic/633, generic/696, generic/697 failure on btrfs with rc2/rc3
Date: Fri, 17 Jul 2026 16:29:26 +0930 [thread overview]
Message-ID: <31464b3b-a183-4dfd-a8e7-2c6c45c2ee5c@gmx.com> (raw)
In-Reply-To: <9b3313bd-cdb2-455a-9dcf-e1106276974f@gmx.com>
My bad, forgot to Cc fstests.
在 2026/7/17 16:27, Qu Wenruo 写道:
> Hi,
>
> It looks like 539dce114465 ("fs: refuse O_TMPFILE creation with an
> unmapped fsuid or fsgid") has changed the behavior that the above tests
> will fail on btrfs/ext4/xfs:
>
> FSTYP -- ext4
> PLATFORM -- Linux/x86_64 btrfs-vm 7.2.0-rc3-custom+ #411 SMP
> PREEMPT_DYNAMIC Fri Jul 17 16:24:34 ACST 2026
> MKFS_OPTIONS -- -F /dev/mapper/test-scratch1
> MOUNT_OPTIONS -- -o acl,user_xattr /dev/mapper/test-scratch1 /mnt/scratch
>
> generic/633 1s ... - output mismatch (see /home/adam/xfstests/results//
> generic/633.out.bad)
> --- tests/generic/633.out 2022-05-11 11:25:30.816666664 +0930
> +++ /home/adam/xfstests/results//generic/633.out.bad 2026-07-17
> 16:25:45.033967541 +0930
> @@ -1,2 +1,4 @@
> QA output created by 633
> Silence is golden
> +utils.c: 948: openat_tmpfile_supported - Value too large for
> defined data type - failure: create
> +utils.c: 948: openat_tmpfile_supported - Value too large for
> defined data type - failure: create
> ...
> (Run 'diff -u /home/adam/xfstests/tests/generic/633.out /home/adam/
> xfstests/results//generic/633.out.bad' to see the entire diff)
> Ran: generic/633
> Failures: generic/633
> Failed 1 of 1 tests
>
> Did a quick search but didn't hit an exact fix.
>
> I guess we need to update the test case to avoid the EOVERFLOW errors?
>
> Thanks,
> Qu
>
parent reply other threads:[~2026-07-17 6:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9b3313bd-cdb2-455a-9dcf-e1106276974f@gmx.com>]
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=31464b3b-a183-4dfd-a8e7-2c6c45c2ee5c@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=brauner@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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