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-kernel@vger.kernel.org>, <linux-bcachefs@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [bcachefs] d1b0f9aa73: xfstests.generic.094.fail
Date: Mon, 12 May 2025 14:28:01 +0800 [thread overview]
Message-ID: <202505121327.7f0fe895-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.094.fail" on:
commit: d1b0f9aa73fe50ee5276708e33d77c4e7054e555 ("bcachefs: Rework fiemap transaction restart handling")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: xfstests
version: xfstests-x86_64-8467552f-1_20241215
with following parameters:
disk: 4HDD
fs: bcachefs
test: generic-094
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (Skylake) with 28G 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/202505121327.7f0fe895-lkp@intel.com
2025-05-11 07:30:51 export TEST_DIR=/fs/sda1
2025-05-11 07:30:51 export TEST_DEV=/dev/sda1
2025-05-11 07:30:51 export FSTYP=bcachefs
2025-05-11 07:30:51 export SCRATCH_MNT=/fs/scratch
2025-05-11 07:30:51 mkdir /fs/scratch -p
2025-05-11 07:30:51 export SCRATCH_DEV=/dev/sda4
2025-05-11 07:30:51 echo generic/094
2025-05-11 07:30:51 ./check generic/094
FSTYP -- bcachefs
PLATFORM -- Linux/x86_64 lkp-skl-d01 6.15.0-rc3-00024-gd1b0f9aa73fe #1 SMP PREEMPT_DYNAMIC Sun May 11 15:03:18 CST 2025
MKFS_OPTIONS -- /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
generic/094 - output mismatch (see /lkp/benchmarks/xfstests/results//generic/094.out.bad)
--- tests/generic/094.out 2024-12-15 06:14:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/094.out.bad 2025-05-11 07:31:04.283558895 +0000
@@ -1,3 +1,11 @@
QA output created by 094
fiemap run with sync
+ERROR: couldn't find extent at 241
+map is 'DPPHDDHHPHPHHHHDHDHDPDDPDPPPHDDHDDPPHHDDHPDPDHPDHPDDHPPHDPHHPDHPDDPHPPPPDHDPHPHHPDHHDPHDPPDHDDDPPDPPPPPPPDPHDDPPDDPPHDDPDHPHPDPHHDPDHDDPDHDDDDHDPDDPDHHDHPPHPPPDPHPHHPPDHDDHDHDDHDHDPDPDHHPHDHHDHDDDDPHPDHDDHPPHHHPDDPHHDHDPPHDPDPDPHHPPDHPDPPDHDDPPPHPPHDHPPPPHHPPDPD'
+logical: [ 241.. 241] phys: 417880.. 417880 flags: 0x101 tot: 0
+Problem comparing fiemap and map
fiemap run without sync
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/094.out /lkp/benchmarks/xfstests/results//generic/094.out.bad' to see the entire diff)
Ran: generic/094
Failures: generic/094
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250512/202505121327.7f0fe895-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-12 6:28 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=202505121327.7f0fe895-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@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 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.