From: Tejun Heo <tj@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
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
Subject: Re: [tj-sched-ext:for-next] [sched_ext] 7900aa699c: kernel-selftests-bpf.sched_ext.runner.init_enable_count_#.fail
Date: Fri, 14 Nov 2025 03:52:44 -1000 [thread overview]
Message-ID: <aRc0LFnfbtMe16vy@slm.duckdns.org> (raw)
In-Reply-To: <202511141028.39aed7d5-lkp@intel.com>
Hello,
On Fri, Nov 14, 2025 at 10:21:12AM +0800, kernel test robot wrote:
> 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]
Unfortunately, I can't reproduce this failure.
> # ===== 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 =====
Looking at the code, I don't see how init_task_cnt can be lower than
num_pre_forks or how the referenced commit can change that (it only changes
the exit path).
Thanks.
--
tejun
prev parent reply other threads:[~2025-11-14 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 2:21 [tj-sched-ext:for-next] [sched_ext] 7900aa699c: kernel-selftests-bpf.sched_ext.runner.init_enable_count_#.fail kernel test robot
2025-11-14 13:52 ` Tejun Heo [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=aRc0LFnfbtMe16vy@slm.duckdns.org \
--to=tj@kernel.org \
--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=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=sched-ext@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox