From: kernel test robot <oliver.sang@intel.com>
To: Qu Wenruo <wqu@suse.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
David Sterba <dsterba@suse.com>,
"hch@infradead.org" <hch@infradead.org>,
Filipe Manana <fdmanana@suse.com>, <linux-btrfs@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [btrfs] 92a6e5b713: xfstests.btrfs.226.fail
Date: Wed, 12 Feb 2025 12:44:44 +0800 [thread overview]
Message-ID: <202502121035.e70df273-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.btrfs.226.fail" on:
commit: 92a6e5b7138df60388f43065b22d0fd846ab8802 ("btrfs: always fallback to buffered write if the inode requires checksum")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master df5d6180169ae06a2eac57e33b077ad6f6252440]
in testcase: xfstests
version: xfstests-x86_64-8467552f-1_20241215
with following parameters:
disk: 6HDD
fs: btrfs
test: btrfs-226
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (Haswell) with 8G 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/202502121035.e70df273-lkp@intel.com
2025-02-11 13:28:35 export TEST_DIR=/fs/sdb1
2025-02-11 13:28:35 export TEST_DEV=/dev/sdb1
2025-02-11 13:28:35 export FSTYP=btrfs
2025-02-11 13:28:35 export SCRATCH_MNT=/fs/scratch
2025-02-11 13:28:35 mkdir /fs/scratch -p
2025-02-11 13:28:35 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4 /dev/sdb5 /dev/sdb6"
2025-02-11 13:28:35 echo btrfs/226
2025-02-11 13:28:35 ./check btrfs/226
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-hsw-d01 6.14.0-rc1-00040-g92a6e5b7138d #1 SMP PREEMPT_DYNAMIC Tue Feb 11 21:13:29 CST 2025
MKFS_OPTIONS -- /dev/sdb2
MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
btrfs/226 - output mismatch (see /lkp/benchmarks/xfstests/results//btrfs/226.out.bad)
--- tests/btrfs/226.out 2024-12-15 06:14:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//btrfs/226.out.bad 2025-02-11 13:28:41.437083025 +0000
@@ -39,14 +39,11 @@
Testing write against prealloc extent at eof
wrote 65536/65536 bytes at offset 0
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 65536/65536 bytes at offset 65536
-XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
+pwrite: Resource temporarily unavailable
File after write:
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/btrfs/226.out /lkp/benchmarks/xfstests/results//btrfs/226.out.bad' to see the entire diff)
Ran: btrfs/226
Failures: btrfs/226
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250212/202502121035.e70df273-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-02-12 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 4:44 kernel test robot [this message]
2025-02-12 6:22 ` [linux-next:master] [btrfs] 92a6e5b713: xfstests.btrfs.226.fail Qu Wenruo
2025-02-13 2:15 ` Oliver Sang
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=202502121035.e70df273-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=wqu@suse.com \
/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