From: kernel test robot <lkp@intel.com>
To: zhidao su <suzhidao@xiaomi.com>
Cc: oe-kbuild-all@lists.linux.dev, Tejun Heo <tj@kernel.org>
Subject: [linux-next:master 1252/1572] kernel/sched/ext.c:3220:20: error: 'scx_cgroup_rwsem' undeclared; did you mean 'scx_cgroup_ops_rwsem'?
Date: Wed, 15 Oct 2025 04:55:05 +0800 [thread overview]
Message-ID: <202510150406.kosHadG1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 13863a59e410cab46d26751941980dc8f088b9b3
commit: d579dc6eb4fd03c43622cf94ccc8d8b508c6d6ff [1252/1572] sched/ext: Implement cgroup_set_idle() callback
config: parisc-randconfig-002-20251015 (https://download.01.org/0day-ci/archive/20251015/202510150406.kosHadG1-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251015/202510150406.kosHadG1-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/202510150406.kosHadG1-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/sched/build_policy.c:62:
kernel/sched/ext.c: In function 'scx_group_set_idle':
>> kernel/sched/ext.c:3220:20: error: 'scx_cgroup_rwsem' undeclared (first use in this function); did you mean 'scx_cgroup_ops_rwsem'?
percpu_down_read(&scx_cgroup_rwsem);
^~~~~~~~~~~~~~~~
scx_cgroup_ops_rwsem
kernel/sched/ext.c:3220:20: note: each undeclared identifier is reported only once for each function it appears in
kernel/sched/ext.c: In function 'scx_vexit':
kernel/sched/ext.c:4411:2: warning: function 'scx_vexit' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
vscnprintf(ei->msg, SCX_EXIT_MSG_LEN, fmt, args);
^~~~~~~~~~
In file included from kernel/sched/build_policy.c:62:
kernel/sched/ext.c: In function '__bstr_format':
kernel/sched/ext.c:6324:6: warning: function '__bstr_format' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
bprintf_data.bin_args);
^~~~~~~~~~~~
vim +3220 kernel/sched/ext.c
3215
3216 void scx_group_set_idle(struct task_group *tg, bool idle)
3217 {
3218 struct scx_sched *sch = scx_root;
3219
> 3220 percpu_down_read(&scx_cgroup_rwsem);
3221
3222 if (scx_cgroup_enabled && SCX_HAS_OP(sch, cgroup_set_idle))
3223 SCX_CALL_OP(sch, SCX_KF_UNLOCKED, cgroup_set_idle, NULL,
3224 tg_cgrp(tg), idle);
3225
3226 /* Update the task group's idle state */
3227 tg->scx.idle = idle;
3228
3229 percpu_up_read(&scx_cgroup_rwsem);
3230 }
3231
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-14 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202510150406.kosHadG1-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=suzhidao@xiaomi.com \
--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.