From: kernel test robot <oliver.sang@intel.com>
To: John Garry <john.g.garry@oracle.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
<linux-block@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [block] 64b582ca88: xfstests.generic.351.fail
Date: Fri, 30 Aug 2024 15:03:52 +0800 [thread overview]
Message-ID: <202408301415.8923e617-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.351.fail" on:
commit: 64b582ca88ca11400467b282d5fa3b870ded1c11 ("block: Read max write zeroes once for __blkdev_issue_write_zeroes()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master d5d547aa7b51467b15d9caa86b116f8c2507c72a]
[test failed on linux-next/master b18bbfc14a38b5234e09c2adcf713e38063a7e6e]
in testcase: xfstests
version: xfstests-x86_64-d9423fec-1_20240826
with following parameters:
disk: 4HDD
fs: f2fs
test: generic-351
compiler: gcc-12
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/202408301415.8923e617-oliver.sang@intel.com
2024-08-29 11:48:35 export TEST_DIR=/fs/sda1
2024-08-29 11:48:35 export TEST_DEV=/dev/sda1
2024-08-29 11:48:35 export FSTYP=f2fs
2024-08-29 11:48:35 export SCRATCH_MNT=/fs/scratch
2024-08-29 11:48:35 mkdir /fs/scratch -p
2024-08-29 11:48:35 export SCRATCH_DEV=/dev/sda4
2024-08-29 11:48:35 export MKFS_OPTIONS="-f"
2024-08-29 11:48:35 echo generic/351
2024-08-29 11:48:35 ./check generic/351
FSTYP -- f2fs
PLATFORM -- Linux/x86_64 lkp-skl-d02 6.10.0-12052-g64b582ca88ca #1 SMP PREEMPT_DYNAMIC Wed Aug 28 21:41:11 CST 2024
MKFS_OPTIONS -- -f /dev/sda4
MOUNT_OPTIONS -- -o acl,user_xattr /dev/sda4 /fs/scratch
generic/351 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/351.out.bad)
--- tests/generic/351.out 2024-08-26 19:09:50.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/351.out.bad 2024-08-29 11:49:27.839575963 +0000
@@ -25,7 +25,7 @@
Destroy device
Create w/o unmap or writesame and format
Zero punch, no fallback available
-fallocate: Operation not supported
+fallocate: Remote I/O error
Zero range, write fallback
Check contents
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/351.out /lkp/benchmarks/xfstests/results//generic/351.out.bad' to see the entire diff)
Ran: generic/351
Failures: generic/351
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240830/202408301415.8923e617-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-08-30 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 7:03 kernel test robot [this message]
2024-08-30 7:23 ` [linus:master] [block] 64b582ca88: xfstests.generic.351.fail John Garry
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=202408301415.8923e617-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.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