All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <yi1.lai@intel.com>
To: Dave Chinner <david@fromorbit.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, yi1.lai@intel.com
Subject: [dgc-xfs:log-verification-1] [xfs]  bbf33f240f: xfstests.generic.450/451/453.fail
Date: Thu, 17 Sep 2026 10:03:11 +0800	[thread overview]
Message-ID: <202609170902.2be2db11-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "xfstests.generic.450/451/453.fail" on:

commit: bbf33f240f9bd46857bf73a5d6f26724f58ed76f ("xfs: validate the unmount record during recovery") https://git.kernel.org/cgit/linux/kernel/git/dgc/linux-xfs.git log-verification-1

in testcase: xfstests
version: xfstests-x86_64-56c410ad-1_20260817
with following parameters:

	disk: 4HDD
	fs: xfs
	test: generic-group-45


config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (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 <yi1.lai@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202609170902.2be2db11-lkp@intel.com

2026-09-16 11:14:08 cd /lkp/benchmarks/xfstests
2026-09-16 11:14:09 export TEST_DIR=/fs/sda1
2026-09-16 11:14:09 export TEST_DEV=/dev/sda1
2026-09-16 11:14:09 export FSTYP=xfs
2026-09-16 11:14:09 export SCRATCH_MNT=/fs/scratch
2026-09-16 11:14:09 mkdir /fs/scratch -p
2026-09-16 11:14:09 export SCRATCH_DEV=/dev/sda4
2026-09-16 11:14:09 export SCRATCH_LOGDEV=/dev/sda2
meta-data=/dev/sda1              isize=512    agcount=4, agsize=13107200 blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=1
         =                       reflink=1    bigtime=1 inobtcount=1 nrext64=1
         =                       exchange=1   metadir=0
data     =                       bsize=4096   blocks=52428800, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1, parent=1
log      =internal log           bsize=4096   blocks=25600, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
         =                       rgcount=0    rgsize=0 extents
         =                       zoned=0      start=0 reserved=0
2026-09-16 11:14:10 export MKFS_OPTIONS="-mreflink=1"
2026-09-16 11:14:10 sed "s:^:generic/:" /lkp/benchmarks/xfstests/tests/generic-group-45
2026-09-16 11:14:10 ./check -E tests/exclude/xfs generic/450 generic/451 generic/453
FSTYP         -- xfs (non-debug)
PLATFORM      -- Linux/x86_64 lkp-skl-d07 7.3.0-rc2+ #1 SMP PREEMPT_DYNAMIC Wed Sep 16 18:57:50 CST 2026
MKFS_OPTIONS  -- -f -mreflink=1 /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch

generic/450        [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/450.out.bad)
    --- tests/generic/450.out   2026-08-17 23:41:54.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//generic/450.out.bad   2026-09-16 11:14:14.376762747 +0000
    @@ -1,11 +1,7 @@
     QA output created by 450
    -buffer read the first sector within EOF
    -buffer read the second block contains EOF
    -buffer read a sector at (after) EOF
    -buffer read the last sector past EOF
    -buffer read at far away from EOF
    -direct read the first sector within EOF
    ...
    (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/450.out /lkp/benchmarks/xfstests/results//generic/450.out.bad'  to see the entire diff)
check: possible mount failures (see /lkp/benchmarks/xfstests/results//generic/450.mountfail)
generic/451        [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/451.out.bad)
    --- tests/generic/451.out   2026-08-17 23:41:54.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//generic/451.out.bad   2026-09-16 11:14:15.227462526 +0000
    @@ -1,2 +1,7 @@
     QA output created by 451
    -Silence is golden
    +mount: /fs/sda1: fsconfig() failed: Structure needs cleaning.
    +       dmesg(1) may have more information after failed mount system call.
    +common/rc: retrying test device mount with external set
    +mount: /fs/sda1: fsconfig() failed: Structure needs cleaning.
    +       dmesg(1) may have more information after failed mount system call.
    ...
    (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/451.out /lkp/benchmarks/xfstests/results//generic/451.out.bad'  to see the entire diff)
check: possible mount failures (see /lkp/benchmarks/xfstests/results//generic/451.mountfail)
generic/453        [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/453.out.bad)
    --- tests/generic/453.out   2026-08-17 23:41:54.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//generic/453.out.bad   2026-09-16 11:14:16.035987245 +0000
    @@ -1,6 +1,7 @@
     QA output created by 453
    -Format and mount
    -Create files
    -Test files
    -Uniqueness of inodes?
    -Test XFS online scrub, if applicable
    +mount: /fs/sda1: fsconfig() failed: Structure needs cleaning.
    ...
    (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/453.out /lkp/benchmarks/xfstests/results//generic/453.out.bad'  to see the entire diff)
check: possible mount failures (see /lkp/benchmarks/xfstests/results//generic/453.mountfail)
Ran: generic/450 generic/451 generic/453
Failures: generic/450 generic/451 generic/453
Failed 3 of 3 tests




The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260917/202609170902.2be2db11-lkp@intel.com



--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2026-09-17  2:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202609170902.2be2db11-lkp@intel.com \
    --to=yi1.lai@intel.com \
    --cc=david@fromorbit.com \
    --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 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.