From: kernel test robot <oliver.sang@intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Dan Schatzberg <dschatzberg@meta.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrea Righi <arighi@nvidia.com>, <sched-ext@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [tj-sched-ext:for-next] [sched_ext] 7900aa699c: kernel-selftests-bpf.sched_ext.runner.init_enable_count_#.fail
Date: Fri, 14 Nov 2025 10:21:12 +0800 [thread overview]
Message-ID: <202511141028.39aed7d5-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests-bpf.sched_ext.runner.init_enable_count_#.fail" on:
commit: 7900aa699c34401cf5d0c701d9ef72880ddc1a83 ("sched_ext: Fix cgroup exit ordering by moving sched_ext_free() to finish_task_switch()")
https://git.kernel.org/cgit/linux/kernel/git/tj/sched_ext.git for-next
[test failed on linux-next/master b179ce312bafcb8c68dc718e015aee79b7939ff0]
in testcase: kernel-selftests-bpf
version:
with following parameters:
group: sched_ext
config: x86_64-rhel-9.4-bpf
compiler: gcc-14
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Kaby 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/202511141028.39aed7d5-lkp@intel.com
# ===== START =====
# TEST: init_enable_count
# DESCRIPTION: Verify we correctly count the occurrences of init, enable, etc callbacks.
# OUTPUT:
# ERR: init_enable_count.c:63
# Expected skel->bss->init_task_cnt >= num_pre_forks (611 >= 1024)
# not ok 9 init_enable_count #
# ===== END =====
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251114/202511141028.39aed7d5-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-11-14 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 2:21 kernel test robot [this message]
2025-11-14 13:52 ` [tj-sched-ext:for-next] [sched_ext] 7900aa699c: kernel-selftests-bpf.sched_ext.runner.init_enable_count_#.fail Tejun Heo
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=202511141028.39aed7d5-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=arighi@nvidia.com \
--cc=dschatzberg@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@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 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.