From: kernel test robot <oliver.sang@intel.com>
To: Andrei Topala <topala.andrei@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<netfs@lists.linux.dev>, <ecryptfs@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-nfs@vger.kernel.org>,
<linux-unionfs@vger.kernel.org>, <linux-cifs@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
"Andrei Topala" <topala.andrei@gmail.com>,
<oliver.sang@intel.com>
Subject: Re: [PATCH] fs: allow rename across bind mounts on same superblock
Date: Tue, 30 Dec 2025 13:57:42 +0800 [thread overview]
Message-ID: <202512301036.b3179a4b-lkp@intel.com> (raw)
In-Reply-To: <20251223173803.1623903-1-topala.andrei@gmail.com>
Hello,
kernel test robot noticed "xfstests.generic.633.fail" on:
commit: 6c7ce82ab1bf6ff8bf562d830a5e9a2dd26b4ebb ("[PATCH] fs: allow rename across bind mounts on same superblock")
url: https://github.com/intel-lab-lkp/linux/commits/Andrei-Topala/fs-allow-rename-across-bind-mounts-on-same-superblock/20251224-020432
base: https://git.kernel.org/cgit/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/all/20251223173803.1623903-1-topala.andrei@gmail.com/
patch subject: [PATCH] fs: allow rename across bind mounts on same superblock
in testcase: xfstests
version: xfstests-x86_64-a668057f-1_20251209
with following parameters:
disk: 4HDD
fs: ext2
test: generic-633
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202512301036.b3179a4b-lkp@intel.com
2025-12-28 19:38:18 cd /lkp/benchmarks/xfstests
2025-12-28 19:38:18 export TEST_DIR=/fs/sdb1
2025-12-28 19:38:18 export TEST_DEV=/dev/sdb1
2025-12-28 19:38:18 export FSTYP=ext2
2025-12-28 19:38:18 export SCRATCH_MNT=/fs/scratch
2025-12-28 19:38:18 mkdir /fs/scratch -p
2025-12-28 19:38:18 export SCRATCH_DEV=/dev/sdb4
2025-12-28 19:38:18 echo generic/633
2025-12-28 19:38:18 ./check -E tests/exclude/ext2 generic/633
FSTYP -- ext2
PLATFORM -- Linux/x86_64 lkp-skl-d03 6.19.0-rc1-00037-g6c7ce82ab1bf #1 SMP PREEMPT_DYNAMIC Mon Dec 29 01:50:58 CST 2025
MKFS_OPTIONS -- -F /dev/sdb4
MOUNT_OPTIONS -- -o acl,user_xattr /dev/sdb4 /fs/scratch
generic/633 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/633.out.bad)
--- tests/generic/633.out 2025-12-09 15:20:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/633.out.bad 2025-12-28 19:41:48.101143921 +0000
@@ -1,2 +1,4 @@
QA output created by 633
Silence is golden
+vfstest.c: 199: rename_crossing_mounts - Success - failure: renameat
+vfstest.c: 2418: run_test - Success - failure: cross mount rename
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/633.out /lkp/benchmarks/xfstests/results//generic/633.out.bad' to see the entire diff)
Ran: generic/633
Failures: generic/633
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251230/202512301036.b3179a4b-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-30 5:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 17:38 [PATCH] fs: allow rename across bind mounts on same superblock Andrei Topala
2025-12-23 17:51 ` Al Viro
[not found] ` <CAF8SvsB0yQC7Meni=UQEehaT5YBQx2uEas8irhg3vWstdM_JVA@mail.gmail.com>
2025-12-23 18:59 ` Al Viro
2025-12-23 23:59 ` Andrei Topala
2025-12-30 5:57 ` kernel test robot [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=202512301036.b3179a4b-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=jack@suse.cz \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netfs@lists.linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=topala.andrei@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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.