From: Vlastimil Babka <vbabka@suse.cz>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, linux-mm@kvack.org
Subject: Re: [vbabka:b4/sheaves-for-all-rebased] [slab] 9b0317d1c2: xfstests.generic.629.fail
Date: Mon, 12 Jan 2026 09:34:20 +0100 [thread overview]
Message-ID: <d7263d12-e6e5-48d9-85b5-0937f7c0dac9@suse.cz> (raw)
In-Reply-To: <202601121022.41666cea-lkp@intel.com>
On 1/12/26 03:54, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed "xfstests.generic.629.fail" on:
>
> commit: 9b0317d1c2ed590d69d39eba701cd3eb082ecc31 ("slab: remove cpu (partial) slabs usage from allocation paths")
> https://git.kernel.org/cgit/linux/kernel/git/vbabka/linux.git b4/sheaves-for-all-rebased
>
> in testcase: xfstests
> version: xfstests-x86_64-df16c93a-1_20260105
> with following parameters:
>
> disk: 4HDD
> fs: btrfs
> test: generic-629
>
>
>
> 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/202601121022.41666cea-lkp@intel.com
>
> 2026-01-11 11:59:36 cd /lkp/benchmarks/xfstests
> 2026-01-11 11:59:37 export TEST_DIR=/fs/sdb1
> 2026-01-11 11:59:37 export TEST_DEV=/dev/sdb1
> 2026-01-11 11:59:37 export FSTYP=btrfs
> 2026-01-11 11:59:37 export SCRATCH_MNT=/fs/scratch
> 2026-01-11 11:59:37 mkdir /fs/scratch -p
> 2026-01-11 11:59:37 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4"
> 2026-01-11 11:59:37 echo generic/629
> 2026-01-11 11:59:37 ./check generic/629
> FSTYP -- btrfs
> PLATFORM -- Linux/x86_64 lkp-skl-d03 6.19.0-rc1-00010-g9b0317d1c2ed #1 SMP PREEMPT_DYNAMIC Sun Jan 11 19:50:05 CST 2026
> MKFS_OPTIONS -- /dev/sdb2
> MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
>
> generic/629 _check_dmesg: something found in dmesg (see /lkp/benchmarks/xfstests/results//generic/629.dmesg)
Hm I didn't notice anything suspicious in dmesg.xz - any idea what this
refers to?
> Ran: generic/629
> Failures: generic/629
> Failed 1 of 1 tests
>
>
>
>
> The kernel config and materials to reproduce are available at:
> https://download.01.org/0day-ci/archive/20260112/202601121022.41666cea-lkp@intel.com
>
>
>
prev parent reply other threads:[~2026-01-12 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 2:54 kernel test robot
2026-01-12 8:34 ` Vlastimil Babka [this message]
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=d7263d12-e6e5-48d9-85b5-0937f7c0dac9@suse.cz \
--to=vbabka@suse.cz \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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