From: kernel test robot <oliver.sang@intel.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
<linux-xfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [iomap] f8eaf79406: xfstests.generic.439.fail
Date: Thu, 20 Nov 2025 14:01:35 +0800 [thread overview]
Message-ID: <202511201341.e536bf55-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "xfstests.generic.439.fail" on:
commit: f8eaf79406fe9415db0e7a5c175b50cb01265199 ("iomap: simplify ->read_folio_range() error handling for reads")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master fe4d0dea039f2befb93f27569593ec209843b0f5]
in testcase: xfstests
version: xfstests-x86_64-5b75444b-1_20251117
with following parameters:
disk: 4HDD
fs: xfs
test: generic-439
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (Skylake) with 16G 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/202511201341.e536bf55-lkp@intel.com
2025-11-19 08:42:31 cd /lkp/benchmarks/xfstests
2025-11-19 08:42:32 export TEST_DIR=/fs/sda1
2025-11-19 08:42:32 export TEST_DEV=/dev/sda1
2025-11-19 08:42:32 export FSTYP=xfs
2025-11-19 08:42:32 export SCRATCH_MNT=/fs/scratch
2025-11-19 08:42:32 mkdir /fs/scratch -p
2025-11-19 08:42:32 export SCRATCH_DEV=/dev/sda4
2025-11-19 08:42:32 export SCRATCH_LOGDEV=/dev/sda2
meta-data=/dev/sda1 isize=512 agcount=4, agsize=13107200 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=1
= reflink=1 bigtime=1 inobtcount=1 nrext64=1
= exchange=0 metadir=0
data = bsize=4096 blocks=52428800, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=0
log =internal log bsize=4096 blocks=25600, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
= rgcount=0 rgsize=0 extents
2025-11-19 08:42:33 export MKFS_OPTIONS=-mreflink=1
2025-11-19 08:42:33 echo generic/439
2025-11-19 08:42:33 ./check generic/439
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 lkp-skl-d07 6.18.0-rc1-00033-gf8eaf79406fe #1 SMP PREEMPT_DYNAMIC Wed Nov 19 16:30:42 CST 2025
MKFS_OPTIONS -- -f -mreflink=1 /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
generic/439 _check_dmesg: something found in dmesg (see /lkp/benchmarks/xfstests/results//generic/439.dmesg)
Ran: generic/439
Failures: generic/439
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251120/202511201341.e536bf55-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-11-20 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 6:01 kernel test robot [this message]
2025-11-20 16:02 ` [linux-next:master] [iomap] f8eaf79406: xfstests.generic.439.fail Joanne Koong
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=202511201341.e536bf55-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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.