From: kernel test robot <oliver.sang@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-bcachefs@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [bcachefs] aee94970fb: xfstests.generic.173/174.fail
Date: Wed, 20 Aug 2025 15:23:12 +0800 [thread overview]
Message-ID: <202508200820.7f866400-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.173/174.fail" on:
commit: aee94970fb69ca330ecd0d4eb8a5e5d63f6ee649 ("bcachefs: Increase BCH_MIN_NR_NBUCKETS")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 3ac864c2d9bb8608ee236e89bf561811613abfce]
in testcase: xfstests
version: xfstests-x86_64-e1e4a0ea-1_20250714
with following parameters:
disk: 4HDD
fs: bcachefs
test: generic-scratch-reflink-08
config: x86_64-rhel-9.4-func
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/202508200820.7f866400-lkp@intel.com
generic/173 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/173.out.bad)
--- tests/generic/173.out 2025-07-14 17:48:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/173.out.bad 2025-08-18 10:06:20.148006154 +0000
@@ -1,7 +1,3 @@
QA output created by 173
Format and mount
Reformat with appropriate size
-Create a big file and reflink it
-Allocate the rest of the space
-mmap CoW the big file
-Remount and try CoW again
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/173.out /lkp/benchmarks/xfstests/results//generic/173.out.bad' to see the entire diff)
generic/174 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/174.out.bad)
--- tests/generic/174.out 2025-07-14 17:48:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/174.out.bad 2025-08-18 10:06:25.277802711 +0000
@@ -1,9 +1,3 @@
QA output created by 174
Format and mount
Reformat with appropriate size
-Create a big file and reflink it
-Allocate the rest of the space
-CoW the big file
-pwrite: No space left on device
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/174.out /lkp/benchmarks/xfstests/results//generic/174.out.bad' to see the entire diff)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250820/202508200820.7f866400-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-20 7:23 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=202508200820.7f866400-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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 NNTP newsgroup(s).