From: kernel test robot <oliver.sang@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Christian Brauner <brauner@kernel.org>,
David Hildenbrand <david@redhat.com>,
Christoph Hellwig <hch@lst.de>, Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-fsdevel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [mm] 60a70e6143: xfstests.generic.363.fail
Date: Tue, 11 Nov 2025 15:05:49 +0800 [thread overview]
Message-ID: <202511111513.2c44a63e-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.363.fail" on:
commit: 60a70e61430b2d568bc5e96f629c5855ee159ace ("mm: Use folio_next_pos()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 9c0826a5d9aa4d52206dd89976858457a2a8a7ed]
in testcase: xfstests
version: xfstests-x86_64-2cba4b54-1_20251020
with following parameters:
disk: 4HDD
fs: ext4
test: generic-363
config: x86_64-rhel-9.4-func
compiler: gcc-14
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/202511111513.2c44a63e-lkp@intel.com
2025-11-09 02:50:19 cd /lkp/benchmarks/xfstests
2025-11-09 02:50:19 export TEST_DIR=/fs/sda1
2025-11-09 02:50:19 export TEST_DEV=/dev/sda1
2025-11-09 02:50:19 export FSTYP=ext4
2025-11-09 02:50:19 export SCRATCH_MNT=/fs/scratch
2025-11-09 02:50:19 mkdir /fs/scratch -p
2025-11-09 02:50:19 export SCRATCH_DEV=/dev/sda4
2025-11-09 02:50:19 echo generic/363
2025-11-09 02:50:19 ./check -E tests/exclude/ext4 generic/363
FSTYP -- ext4
PLATFORM -- Linux/x86_64 lkp-skl-d02 6.18.0-rc1-00010-g60a70e61430b #1 SMP PREEMPT_DYNAMIC Sun Nov 9 10:29:45 CST 2025
MKFS_OPTIONS -- -F /dev/sda4
MOUNT_OPTIONS -- -o acl,user_xattr /dev/sda4 /fs/scratch
generic/363 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/363.out.bad)
--- tests/generic/363.out 2025-10-20 16:48:15.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/363.out.bad 2025-11-09 02:51:05.593092955 +0000
@@ -1,2 +1,9399 @@
QA output created by 363
fsx -q -S 0 -e 1 -N 100000
+READ BAD DATA: offset = 0x28db4, size = 0xed5, fname = /fs/sda1/junk
+OFFSET GOOD BAD RANGE
+0x29a39 0x0000 0xa079 0x0
+operation# (mod 256) for the bad data may be 121
+0x29a3a 0x0000 0x79a6 0x1
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/363.out /lkp/benchmarks/xfstests/results//generic/363.out.bad' to see the entire diff)
Ran: generic/363
Failures: generic/363
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251111/202511111513.2c44a63e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-11 7:06 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=202511111513.2c44a63e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=willy@infradead.org \
/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.