From: kernel test robot <oliver.sang@intel.com>
To: GuangFei Luo <luogf2025@163.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-fsdevel@vger.kernel.org>, <viro@zeniv.linux.org.uk>,
<brauner@kernel.org>, <jack@suse.cz>,
<linux-kernel@vger.kernel.org>, GuangFei Luo <luogf2025@163.com>,
<stable@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH] mount: fix duplicate mounts using the new mount API
Date: Wed, 29 Oct 2025 11:06:06 +0800 [thread overview]
Message-ID: <202510291004.24ca6327-lkp@intel.com> (raw)
In-Reply-To: <20251025024934.1350492-1-luogf2025@163.com>
Hello,
kernel test robot noticed "xfstests.xfs.153.fail" on:
commit: ad04c4e00fd850d57b3a07e1920e4e44e6dc393b ("[PATCH] mount: fix duplicate mounts using the new mount API")
url: https://github.com/intel-lab-lkp/linux/commits/GuangFei-Luo/mount-fix-duplicate-mounts-using-the-new-mount-API/20251025-105257
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git 566771afc7a81e343da9939f0bd848d3622e2501
patch link: https://lore.kernel.org/all/20251025024934.1350492-1-luogf2025@163.com/
patch subject: [PATCH] mount: fix duplicate mounts using the new mount API
in testcase: xfstests
version: xfstests-x86_64-2cba4b54-1_20251020
with following parameters:
disk: 4HDD
fs: xfs
test: xfs-153
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (Skylake) with 16G 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/202510291004.24ca6327-lkp@intel.com
2025-10-28 06:08:21 cd /lkp/benchmarks/xfstests
2025-10-28 06:08:23 export TEST_DIR=/fs/sda1
2025-10-28 06:08:23 export TEST_DEV=/dev/sda1
2025-10-28 06:08:23 export FSTYP=xfs
2025-10-28 06:08:23 export SCRATCH_MNT=/fs/scratch
2025-10-28 06:08:23 mkdir /fs/scratch -p
2025-10-28 06:08:23 export SCRATCH_DEV=/dev/sda4
2025-10-28 06:08:23 export SCRATCH_LOGDEV=/dev/sda2
2025-10-28 06:08:23 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2025-10-28 06:08:23 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2025-10-28 06:08:23 echo xfs/153
2025-10-28 06:08:23 ./check xfs/153
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 lkp-skl-d06 6.18.0-rc2-00237-gad04c4e00fd8 #1 SMP PREEMPT_DYNAMIC Tue Oct 28 13:58:10 CST 2025
MKFS_OPTIONS -- -f /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
xfs/153 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//xfs/153.out.bad)
--- tests/xfs/153.out 2025-10-20 16:48:15.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//xfs/153.out.bad 2025-10-28 06:08:30.851957601 +0000
@@ -11,119 +11,6 @@
[ROOT] 0 0 0 00 [--------] 3 0 0 00 [--------] 0 0 0 00 [--------]
*** report initial settings
-[ROOT] 0 0 0 00 [--------] 3 0 0 00 [--------] 0 0 0 00 [--------]
-[NAME] 0 200 1000 00 [--------] 1 4 10 00 [--------] 0 0 0 00 [--------]
-
-*** push past the soft inode limit
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/153.out /lkp/benchmarks/xfstests/results//xfs/153.out.bad' to see the entire diff)
Ran: xfs/153
Failures: xfs/153
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251029/202510291004.24ca6327-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-10-29 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 2:49 [PATCH] mount: fix duplicate mounts using the new mount API GuangFei Luo
2025-10-25 3:36 ` Al Viro
2025-10-25 6:02 ` GuangFei Luo
2025-10-31 12:54 ` Christian Brauner
2025-10-31 18:48 ` Al Viro
2025-11-05 11:54 ` Christian Brauner
2025-10-29 3:06 ` 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=202510291004.24ca6327-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luogf2025@163.com \
--cc=oe-lkp@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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.