From: kernel test robot <oliver.sang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Charlie Jenkins <thecharlesjenkins@gmail.com>,
<linux-arch@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [tip:locking/core] [futex] b78b0b6582: kselftests.damon.sysfs_memcg_path_leak.sh.fail
Date: Fri, 7 Aug 2026 16:50:48 +0800 [thread overview]
Message-ID: <202608071053.6db6276e-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kselftests.damon.sysfs_memcg_path_leak.sh.fail" on:
commit: b78b0b65825275f58336a43611a700de174be8c3 ("futex: Use runtime constants for __futex_hash() hot path")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git locking/core
in testcase: kselftests
version: kselftests-x86_64-f5098b6bae76-1_20260727
with following parameters:
group: damon
config: x86_64-rhel-9.4-kselftests
compiler: gcc-14
test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) 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/202608071053.6db6276e-lkp@intel.com
# timeout set to 300
# selftests: damon: sysfs_memcg_path_leak.sh
# unreferenced object 0xffff8881029e0ab8 (size 8):
# comm "swapper/0", pid 1, jiffies 4294668108
# hex dump (first 8 bytes):
# 00 00 d0 02 81 88 ff ff ........
# backtrace (crc 6c1bc6d6):
# __kmalloc_noprof+0x56b/0x830
# futex_init+0x108/0x3c0
# do_one_initcall+0xc3/0x4b0
# do_initcalls+0x215/0x240
# kernel_init_freeable+0x4a1/0x530
# kernel_init+0x18/0x180
# ret_from_fork+0x547/0x870
# ret_from_fork_asm+0x1a/0x30
not ok 13 selftests: damon: sysfs_memcg_path_leak.sh # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260807/202608071053.6db6276e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-08-07 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 8:50 kernel test robot [this message]
2026-08-07 9:01 ` [tip:locking/core] [futex] b78b0b6582: kselftests.damon.sysfs_memcg_path_leak.sh.fail Peter Zijlstra
2026-08-07 14:49 ` SJ Park
2026-08-07 15:23 ` Peter Zijlstra
2026-08-07 17:37 ` Catalin Marinas
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=202608071053.6db6276e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=thecharlesjenkins@gmail.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox