From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen-kernel-zen-kernel:5.10/muqss 1/21] kernel/sched/MuQSS.c:4407:35: warning: no previous prototype for 'schedule_user'
Date: Tue, 29 Dec 2020 11:11:03 +0800 [thread overview]
Message-ID: <202012291155.UXPVulRX-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5532 bytes --]
tree: https://github.com/zen-kernel/zen-kernel 5.10/muqss
head: 5e029bcb673aa73c2a432f5f78f60351821f5b33
commit: 9d6b3eef3a1ec22d4d3c74e0b773ff52d3b3a209 [1/21] MultiQueue Skiplist Scheduler v0.204
config: x86_64-rhel (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/zen-kernel/zen-kernel/commit/9d6b3eef3a1ec22d4d3c74e0b773ff52d3b3a209
git remote add zen-kernel-zen-kernel https://github.com/zen-kernel/zen-kernel
git fetch --no-tags zen-kernel-zen-kernel 5.10/muqss
git checkout 9d6b3eef3a1ec22d4d3c74e0b773ff52d3b3a209
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
kernel/sched/MuQSS.c:241:12: warning: no previous prototype for 'arch_sd_sibling_asym_packing' [-Wmissing-prototypes]
241 | int __weak arch_sd_sibling_asym_packing(void)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:639:6: warning: no previous prototype for 'resched_task' [-Wmissing-prototypes]
639 | void resched_task(struct task_struct *p)
| ^~~~~~~~~~~~
kernel/sched/MuQSS.c:2386:5: warning: no previous prototype for 'sysctl_schedstats' [-Wmissing-prototypes]
2386 | int sysctl_schedstats(struct ctl_table *table, int write, void *buffer,
| ^~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:3076:15: warning: no previous prototype for 'nr_active' [-Wmissing-prototypes]
3076 | unsigned long nr_active(void)
| ^~~~~~~~~
>> kernel/sched/MuQSS.c:4407:35: warning: no previous prototype for 'schedule_user' [-Wmissing-prototypes]
4407 | asmlinkage __visible void __sched schedule_user(void)
| ^~~~~~~~~~~~~
kernel/sched/MuQSS.c:6113:6: warning: no previous prototype for '__do_set_cpus_allowed' [-Wmissing-prototypes]
6113 | void __do_set_cpus_allowed(struct task_struct *p, const struct cpumask *new_mask)
| ^~~~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:6234:6: warning: no previous prototype for 'resched_cpu' [-Wmissing-prototypes]
6234 | void resched_cpu(int cpu)
| ^~~~~~~~~~~
kernel/sched/MuQSS.c:6247:6: warning: no previous prototype for 'select_nohz_load_balancer' [-Wmissing-prototypes]
6247 | void select_nohz_load_balancer(int stop_tick)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:6251:6: warning: no previous prototype for 'set_cpu_sd_state_idle' [-Wmissing-prototypes]
6251 | void set_cpu_sd_state_idle(void) {}
| ^~~~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:6305:6: warning: no previous prototype for 'wake_up_idle_cpu' [-Wmissing-prototypes]
6305 | void wake_up_idle_cpu(int cpu)
| ^~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:6569:6: warning: no previous prototype for 'sched_set_stop_task' [-Wmissing-prototypes]
6569 | void sched_set_stop_task(int cpu, struct task_struct *stop)
| ^~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:7697:6: warning: no previous prototype for 'init_idle_bootup_task' [-Wmissing-prototypes]
7697 | void init_idle_bootup_task(struct task_struct *idle)
| ^~~~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:7721:20: warning: no previous prototype for 'sched_create_group' [-Wmissing-prototypes]
7721 | struct task_group *sched_create_group(struct task_group *parent)
| ^~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:7732:6: warning: no previous prototype for 'sched_online_group' [-Wmissing-prototypes]
7732 | void sched_online_group(struct task_group *tg, struct task_group *parent)
| ^~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:7743:6: warning: no previous prototype for 'sched_destroy_group' [-Wmissing-prototypes]
7743 | void sched_destroy_group(struct task_group *tg)
| ^~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:7749:6: warning: no previous prototype for 'sched_offline_group' [-Wmissing-prototypes]
7749 | void sched_offline_group(struct task_group *tg)
| ^~~~~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:7840:20: warning: initialized field overwritten [-Woverride-init]
7840 | .legacy_cftypes = cpu_legacy_files,
| ^~~~~~~~~~~~~~~~
kernel/sched/MuQSS.c:7840:20: note: (near initialization for 'cpu_cgrp_subsys.legacy_cftypes')
vim +/schedule_user +4407 kernel/sched/MuQSS.c
4405
4406 #ifdef CONFIG_CONTEXT_TRACKING
> 4407 asmlinkage __visible void __sched schedule_user(void)
4408 {
4409 /*
4410 * If we come here after a random call to set_need_resched(),
4411 * or we have been woken up remotely but the IPI has not yet arrived,
4412 * we haven't yet exited the RCU idle mode. Do it here manually until
4413 * we find a better solution.
4414 *
4415 * NB: There are buggy callers of this function. Ideally we
4416 * should warn if prev_state != IN_USER, but that will trigger
4417 * too frequently to make sense yet.
4418 */
4419 enum ctx_state prev_state = exception_enter();
4420 schedule();
4421 exception_exit(prev_state);
4422 }
4423 #endif
4424
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 45676 bytes --]
reply other threads:[~2020-12-29 3:11 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=202012291155.UXPVulRX-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.