From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-kiwi-5.10 303/303] kernel/cpu.c:1098:5: sparse: sparse: symbol '__pause_drain_rq' was not declared. Should it be static?
Date: Thu, 05 Nov 2026 09:39:38 +0100 [thread overview]
Message-ID: <202611050914.le3P7s3D-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android12-kiwi-5.10
head: f012a641c30644ec5bf95cf64d8835854b997f86
commit: e19b8ce907a4ccc2f9dbeba218c50d1ff07fd321 [303/303] ANDROID: cpu/hotplug: add migration to paused_cpus
config: i386-randconfig-2301-20261105 (https://download.01.org/0day-ci/archive/20261105/202611050914.le3P7s3D-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261105/202611050914.le3P7s3D-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/202611050914.le3P7s3D-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/cpu.c:1098:5: sparse: sparse: symbol '__pause_drain_rq' was not declared. Should it be static?
>> kernel/cpu.c:1118:6: sparse: sparse: symbol '__wait_drain_rq' was not declared. Should it be static?
kernel/cpu.c:844:9: sparse: sparse: context imbalance in 'clear_tasks_mm_cpumask' - different lock contexts for basic block
vim +/__pause_drain_rq +1098 kernel/cpu.c
1097
> 1098 int __pause_drain_rq(struct cpumask *cpus)
1099 {
1100 unsigned int cpu;
1101 int err = 0;
1102
1103 /*
1104 * Disabling preemption avoids that one of the stopper, started from
1105 * sched_cpu_drain_rq(), blocks firing draining for the whole cpumask.
1106 */
1107 preempt_disable();
1108 for_each_cpu(cpu, cpus) {
1109 err = sched_cpu_drain_rq(cpu);
1110 if (err)
1111 break;
1112 }
1113 preempt_enable();
1114
1115 return err;
1116 }
1117
> 1118 void __wait_drain_rq(struct cpumask *cpus)
1119 {
1120 unsigned int cpu;
1121
1122 for_each_cpu(cpu, cpus)
1123 sched_cpu_drain_rq_wait(cpu);
1124 }
1125
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-05 8:40 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=202611050914.le3P7s3D-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.