oe-lkp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Christoph Hellwig <hch@lst.de>, <oliver.sang@intel.com>
Subject: [hch-block:blk-limits-base] [loop]  b022aefe4b: xfstests.xfs.513.fail
Date: Wed, 7 Feb 2024 16:14:33 +0800	[thread overview]
Message-ID: <202402071653.9d34be1e-oliver.sang@intel.com> (raw)



Hello,

kernel test robot noticed "xfstests.xfs.513.fail" on:

commit: b022aefe4bb85b8e26a4ea8895bf6cac278f2bfb ("loop: pass queue_limits to blk_mq_alloc_disk")
git://git.infradead.org/users/hch/block.git blk-limits-base

in testcase: xfstests
version: xfstests-x86_64-17324dbc-1_20240115
with following parameters:

	disk: 4HDD
	fs: xfs
	test: xfs-513



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/202402071653.9d34be1e-oliver.sang@intel.com

2024-02-05 10:45:31 export TEST_DIR=/fs/sda1
2024-02-05 10:45:31 export TEST_DEV=/dev/sda1
2024-02-05 10:45:31 export FSTYP=xfs
2024-02-05 10:45:31 export SCRATCH_MNT=/fs/scratch
2024-02-05 10:45:31 mkdir /fs/scratch -p
2024-02-05 10:45:31 export SCRATCH_DEV=/dev/sda4
2024-02-05 10:45:31 export SCRATCH_LOGDEV=/dev/sda2
2024-02-05 10:45:31 export SCRATCH_XFS_LIST_METADATA_FIELDS=u3.sfdir3.hdr.parent.i4
2024-02-05 10:45:31 export SCRATCH_XFS_LIST_FUZZ_VERBS=random
2024-02-05 10:45:31 echo xfs/513
2024-02-05 10:45:31 ./check xfs/513
FSTYP         -- xfs (debug)
PLATFORM      -- Linux/x86_64 lkp-skl-d06 6.8.0-rc2-00068-gb022aefe4bb8 #1 SMP PREEMPT_DYNAMIC Mon Feb  5 15:29:25 CST 2024
MKFS_OPTIONS  -- -f /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch

xfs/513       - output mismatch (see /lkp/benchmarks/xfstests/results//xfs/513.out.bad)
    --- tests/xfs/513.out	2024-01-15 19:11:14.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//xfs/513.out.bad	2024-02-05 10:48:01.403892771 +0000
    @@ -20,6 +20,8 @@
     FORMAT: 
     TEST: "" "pass" "discard" "false"
     TEST: "-o discard" "pass" "discard" "true"
    +[FAILED]: mount /dev/loop0 /fs/sda1/513.mnt -o discard
    +ERROR: did not expect to find "discard" in "rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota"
     TEST: "-o nodiscard" "pass" "discard" "false"
     TEST: "" "pass" "grpid" "false"
    ...
    (Run 'diff -u /lkp/benchmarks/xfstests/tests/xfs/513.out /lkp/benchmarks/xfstests/results//xfs/513.out.bad'  to see the entire diff)

HINT: You _MAY_ be missing kernel fix:
      237d7887ae72 xfs: show the proper user quota options

Ran: xfs/513
Failures: xfs/513
Failed 1 of 1 tests




The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240207/202402071653.9d34be1e-oliver.sang@intel.com



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


                 reply	other threads:[~2024-02-07  8:14 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=202402071653.9d34be1e-oliver.sang@intel.com \
    --to=oliver.sang@intel.com \
    --cc=hch@lst.de \
    --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).