From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-5.4 1/1] init/main.c:251:6: sparse: sparse: symbol 'xbc_namebuf' was not declared. Should it be static?
Date: Sun, 21 Dec 2025 18:27:20 +0800 [thread overview]
Message-ID: <202512211859.amJfn4AI-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android12-5.4
head: 250657e3e4fa0189d0ebf710093551ba4a1ea9c1
commit: dca811b6c4342bf1b98b67e199b9b01d3b3c2166 [1/1] UPSTREAM: bootconfig: init: Allow admin to use bootconfig for kernel command line
config: arm64-randconfig-r113-20250923 (https://download.01.org/0day-ci/archive/20251221/202512211859.amJfn4AI-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251221/202512211859.amJfn4AI-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/202512211859.amJfn4AI-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> init/main.c:251:6: sparse: sparse: symbol 'xbc_namebuf' was not declared. Should it be static?
init/main.c:327:5: sparse: sparse: symbol 'boot_config_checksum' was not declared. Should it be static?
vim +/xbc_namebuf +251 init/main.c
172
173 static const char *argv_init[MAX_INIT_ARGS+2] = { "init", NULL, };
> 174 const char *envp_init[MAX_INIT_ENVS+2] = { "HOME=/", "TERM=linux", NULL, };
175 static const char *panic_later, *panic_param;
176
177 extern const struct obs_kernel_param __setup_start[], __setup_end[];
178
179 static bool __init obsolete_checksetup(char *line)
180 {
181 const struct obs_kernel_param *p;
182 bool had_early_param = false;
183
184 p = __setup_start;
185 do {
186 int n = strlen(p->str);
187 if (parameqn(line, p->str, n)) {
188 if (p->early) {
189 /* Already done in parse_early_param?
190 * (Needs exact match on param part).
191 * Keep iterating, as we can have early
192 * params and __setups of same names 8( */
193 if (line[n] == '\0' || line[n] == '=')
194 had_early_param = true;
195 } else if (!p->setup_func) {
196 pr_warn("Parameter %s is obsolete, ignored\n",
197 p->str);
198 return true;
199 } else if (p->setup_func(line + n))
200 return true;
201 }
202 p++;
203 } while (p < __setup_end);
204
205 return had_early_param;
206 }
207
208 /*
209 * This should be approx 2 Bo*oMips to start (note initial shift), and will
210 * still work even if initially too large, it will just take slightly longer
211 */
212 unsigned long loops_per_jiffy = (1<<12);
213 EXPORT_SYMBOL(loops_per_jiffy);
214
215 static int __init debug_kernel(char *str)
216 {
217 console_loglevel = CONSOLE_LOGLEVEL_DEBUG;
218 return 0;
219 }
220
221 static int __init quiet_kernel(char *str)
222 {
223 console_loglevel = CONSOLE_LOGLEVEL_QUIET;
224 return 0;
225 }
226
227 early_param("debug", debug_kernel);
228 early_param("quiet", quiet_kernel);
229
230 static int __init loglevel(char *str)
231 {
232 int newlevel;
233
234 /*
235 * Only update loglevel value when a correct setting was passed,
236 * to prevent blind crashes (when loglevel being set to 0) that
237 * are quite hard to debug
238 */
239 if (get_option(&str, &newlevel)) {
240 console_loglevel = newlevel;
241 return 0;
242 }
243
244 return -EINVAL;
245 }
246
247 early_param("loglevel", loglevel);
248
249 #ifdef CONFIG_BOOT_CONFIG
250
> 251 char xbc_namebuf[XBC_KEYLEN_MAX] __initdata;
252
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-21 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 10:27 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-05 19:56 [android-common:android12-5.4 1/1] init/main.c:251:6: sparse: sparse: symbol 'xbc_namebuf' was not declared. Should it be static? kernel test robot
2025-12-05 2:56 kernel test robot
2025-10-28 20:18 kernel test robot
2025-10-26 0:03 kernel test robot
2025-09-23 16:10 kernel test robot
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=202512211859.amJfn4AI-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.