[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aRc0LFnfbtMe16vy@slm.duckdns.org>
Date: Fri, 14 Nov 2025 03:52:44 -1000
From: Tejun Heo <tj@...nel.org>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com,
Dan Schatzberg <dschatzberg@...a.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrea Righi <arighi@...dia.com>, sched-ext@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [tj-sched-ext:for-next] [sched_ext] 7900aa699c:
kernel-selftests-bpf.sched_ext.runner.init_enable_count_#.fail
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
Powered by blists - more mailing lists