From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Zicheng Qu <quzicheng@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 3278/3278] include/linux/xsched.h:309:28: error: array type has incomplete element type 'struct cgroup_file'
Date: Wed, 19 Nov 2025 20:12:13 +0800 [thread overview]
Message-ID: <202511192040.YIPXCVFH-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: dfb9bd9242c2350c127d51a126976ed386e9cc48
commit: aafde051ac61687823976cc892fb3c416101d694 [3278/3278] xsched: Add support for CFS quota for cgroups
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20251119/202511192040.YIPXCVFH-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251119/202511192040.YIPXCVFH-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/202511192040.YIPXCVFH-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/xsched/vstream.c:23:
include/linux/xsched.h:276:36: error: field 'css' has incomplete type
276 | struct cgroup_subsys_state css;
| ^~~
>> include/linux/xsched.h:309:28: error: array type has incomplete element type 'struct cgroup_file'
309 | struct cgroup_file xcu_file[NR_XCU_FILE_TYPES];
| ^~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for ARCH_SUPPORTS_SCHED_SOFT_QUOTA
Depends on [n]: CGROUPS [=n]
Selected by [y]:
- ARM64 [=y]
WARNING: unmet direct dependencies detected for HALTPOLL_CPUIDLE
Depends on [n]: CPU_IDLE [=n] && ARCH_CPUIDLE_HALTPOLL [=y] && ARCH_HAS_OPTIMIZED_POLL [=y]
Selected by [y]:
- ARM64 [=y]
vim +309 include/linux/xsched.h
272
273 /* Xsched scheduling control group */
274 struct xsched_group {
275 /* Cgroups controller structure */
276 struct cgroup_subsys_state css;
277
278 /* Control group settings: */
279 int sched_class;
280 int prio;
281
282 /* Bandwidth setting: shares value set by user */
283 u64 shares_cfg;
284 u64 shares_cfg_red;
285 u32 weight;
286 u64 children_shares_sum;
287
288 /* Bandwidth setting: maximal quota in period */
289 s64 quota;
290 /* record the runtime of operators during the period */
291 s64 runtime;
292 s64 period;
293 struct hrtimer quota_timeout;
294 struct work_struct refill_work;
295
296 struct xsched_group_xcu_priv perxcu_priv[XSCHED_NR_CUS];
297
298 /* Groups hierarchcy */
299 struct xsched_group *parent;
300 struct list_head children_groups;
301 struct list_head group_node;
302
303 spinlock_t lock;
304
305 /* for XSE to move in perxcu */
306 struct list_head members;
307
308 /* to control the xcu.{period, quota, shares} files shown or not */
> 309 struct cgroup_file xcu_file[NR_XCU_FILE_TYPES];
310 struct work_struct file_show_work;
311 };
312
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-19 12:12 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=202511192040.YIPXCVFH-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quzicheng@huawei.com \
/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.