From: kernel test robot <lkp@intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: kernel/sched/core.c:9284:38: error: no member named 'scx_weight' in 'struct task_group'
Date: Wed, 17 Sep 2025 02:12:41 +0800 [thread overview]
Message-ID: <202509170230.MwZsJSWa-lkp@intel.com> (raw)
Hi Tejun,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 46a51f4f5edade43ba66b3c151f0e25ec8b69cb6
commit: 6e6558a6bc418f1478c5dc8609d03805364e0cb9 sched_ext, sched/core: Factor out struct scx_task_group
date: 3 months ago
config: x86_64-buildonly-randconfig-004-20250917 (https://download.01.org/0day-ci/archive/20250917/202509170230.MwZsJSWa-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250917/202509170230.MwZsJSWa-lkp@intel.com/reproduce)
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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509170230.MwZsJSWa-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/sched/core.c:9284:38: error: no member named 'scx_weight' in 'struct task_group'
9284 | return sched_weight_from_cgroup(tg->scx_weight);
| ~~ ^
1 error generated.
vim +9284 kernel/sched/core.c
2480c093130f64a kernel/sched/core.c Patrick Bellasi 2019-08-22 9277
e179e80c5d4fef4 kernel/sched/core.c Tejun Heo 2024-09-04 9278 #ifdef CONFIG_GROUP_SCHED_WEIGHT
41082c1d1d2bf6c kernel/sched/core.c Tejun Heo 2024-09-04 9279 static unsigned long tg_weight(struct task_group *tg)
41082c1d1d2bf6c kernel/sched/core.c Tejun Heo 2024-09-04 9280 {
052f1dc7eb02300 kernel/sched.c Peter Zijlstra 2008-02-13 9281 #ifdef CONFIG_FAIR_GROUP_SCHED
41082c1d1d2bf6c kernel/sched/core.c Tejun Heo 2024-09-04 9282 return scale_load_down(tg->shares);
8195136669661fd kernel/sched/core.c Tejun Heo 2024-09-04 9283 #else
8195136669661fd kernel/sched/core.c Tejun Heo 2024-09-04 @9284 return sched_weight_from_cgroup(tg->scx_weight);
8195136669661fd kernel/sched/core.c Tejun Heo 2024-09-04 9285 #endif
41082c1d1d2bf6c kernel/sched/core.c Tejun Heo 2024-09-04 9286 }
41082c1d1d2bf6c kernel/sched/core.c Tejun Heo 2024-09-04 9287
:::::: The code at line 9284 was first introduced by commit
:::::: 8195136669661fdfe54e9a8923c33b31c92fc1da sched_ext: Add cgroup support
:::::: TO: Tejun Heo <tj@kernel.org>
:::::: CC: Tejun Heo <tj@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-09-16 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 18:12 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-08 19:57 kernel/sched/core.c:9284:38: error: no member named 'scx_weight' in 'struct task_group' kernel test robot
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=202509170230.MwZsJSWa-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox