From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android15-6.6-2026-01 1/1] kernel/time/tick-sched.c:212:12: warning: 'tick_cpu' is used uninitialized
Date: Sun, 12 Jul 2026 04:52:25 +0800 [thread overview]
Message-ID: <202607120414.jw7PeLo2-lkp@intel.com> (raw)
Hi Thomas,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android15-6.6-2026-01
head: ef3981c98298123ce7d52b6e12707f16d9f5d254
commit: a94ba5ab288780f141d741107751b4866bc24be3 [1/1] BACKPORT: timekeeping: Use READ/WRITE_ONCE() for tick_do_timer_cpu
config: i386-buildonly-randconfig-006-20260708 (https://download.01.org/0day-ci/archive/20260712/202607120414.jw7PeLo2-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260712/202607120414.jw7PeLo2-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/202607120414.jw7PeLo2-lkp@intel.com/
All warnings (new ones prefixed by >>):
kernel/time/tick-sched.c: In function 'tick_sched_do_timer':
>> kernel/time/tick-sched.c:212:12: warning: 'tick_cpu' is used uninitialized [-Wuninitialized]
212 | if (tick_cpu == cpu) {
| ^
kernel/time/tick-sched.c:188:13: note: 'tick_cpu' was declared here
188 | int tick_cpu, cpu = smp_processor_id();
| ^~~~~~~~
vim +/tick_cpu +212 kernel/time/tick-sched.c
210
211 /* Check, if the jiffies need an update */
> 212 if (tick_cpu == cpu) {
213 tick_do_update_jiffies64(now);
214 trace_android_vh_jiffies_update(NULL);
215 }
216
217 /*
218 * If jiffies update stalled for too long (timekeeper in stop_machine()
219 * or VMEXIT'ed for several msecs), force an update.
220 */
221 if (ts->last_tick_jiffies != jiffies) {
222 ts->stalled_jiffies = 0;
223 ts->last_tick_jiffies = READ_ONCE(jiffies);
224 } else {
225 if (++ts->stalled_jiffies == MAX_STALLED_JIFFIES) {
226 tick_do_update_jiffies64(now);
227 ts->stalled_jiffies = 0;
228 ts->last_tick_jiffies = READ_ONCE(jiffies);
229 }
230 }
231
232 if (ts->inidle)
233 ts->got_idle_tick = 1;
234 }
235
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-11 20:52 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=202607120414.jw7PeLo2-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.