From: kernel test robot <oliver.sang@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-xfs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH 4/4] xfs: reactivate XFS_NEED_INACTIVE inodes from xfs_iget
Date: Wed, 14 Feb 2024 12:00:53 +0800 [thread overview]
Message-ID: <202402141107.4642a3e7-oliver.sang@intel.com> (raw)
In-Reply-To: <20240201005217.1011010-5-david@fromorbit.com>
Hello,
kernel test robot noticed "xfstests.xfs.183.fail" on:
commit: 98e62582b2cc1b05a1075ce816256e8f257a6881 ("[PATCH 4/4] xfs: reactivate XFS_NEED_INACTIVE inodes from xfs_iget")
url: https://github.com/intel-lab-lkp/linux/commits/Dave-Chinner/xfs-make-inode-inactivation-state-changes-atomic/20240201-085509
base: https://git.kernel.org/cgit/fs/xfs/xfs-linux.git for-next
patch link: https://lore.kernel.org/all/20240201005217.1011010-5-david@fromorbit.com/
patch subject: [PATCH 4/4] xfs: reactivate XFS_NEED_INACTIVE inodes from xfs_iget
in testcase: xfstests
version: xfstests-x86_64-c46ca4d1-1_20240205
with following parameters:
disk: 4HDD
fs: xfs
test: xfs-183
compiler: gcc-12
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/202402141107.4642a3e7-oliver.sang@intel.com
2024-02-08 20:30:36 export TEST_DIR=/fs/sda1
2024-02-08 20:30:36 export TEST_DEV=/dev/sda1
2024-02-08 20:30:36 export FSTYP=xfs
2024-02-08 20:30:36 export SCRATCH_MNT=/fs/scratch
2024-02-08 20:30:36 mkdir /fs/scratch -p
2024-02-08 20:30:36 export SCRATCH_DEV=/dev/sda4
2024-02-08 20:30:36 export SCRATCH_LOGDEV=/dev/sda2
2024-02-08 20:30:36 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2024-02-08 20:30:36 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2024-02-08 20:30:36 echo xfs/183
2024-02-08 20:30:36 ./check xfs/183
FSTYP -- xfs (debug)
PLATFORM -- Linux/x86_64 lkp-skl-d06 6.8.0-rc2-00006-g98e62582b2cc #1 SMP PREEMPT_DYNAMIC Thu Feb 8 18:32:20 CST 2024
MKFS_OPTIONS -- -f /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
xfs/183 - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/183.out.bad)
--- tests/xfs/183.out 2024-02-05 17:37:40.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//xfs/183.out.bad 2024-02-08 20:32:06.555798923 +0000
@@ -1,4 +1,4 @@
QA output created by 183
Start original bulkstat_unlink_test with -r switch
Runing extended checks.
-Iteration 0 ... (100 files)passed
+Iteration 0 ... (100 files)ERROR, count(100) != scount(2).
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/183.out /lkp/benchmarks/xfstests/results//xfs/183.out.bad' to see the entire diff)
Ran: xfs/183
Failures: xfs/183
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240214/202402141107.4642a3e7-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-02-14 4:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240201005217.1011010-5-david@fromorbit.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=202402141107.4642a3e7-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).