public inbox for [email protected]
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: Borislav Petkov <[email protected]>
Cc: [email protected],
	GNU/Weeb Mailing List <[email protected]>,
	[email protected], Kees Cook <[email protected]>
Subject: [ammarfaizi2-block:bp/bp/rc0+ 6/11] arch/x86/kernel/cpu/common.c:1415:10: error: 'x86_cap_flags' undeclared; did you mean 'x86_cap_flag'?
Date: Tue, 29 Mar 2022 22:23:07 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block bp/bp/rc0+
head:   2d784fc7295963360594f3de64446aa32841c694
commit: c3b9dcd01973935375ca9d0c67044bea7333d4ef [6/11] x86/cpu: Allow feature bit names from /proc/cpuinfo in clearcpuid=
config: i386-tinyconfig (https://download.01.org/0day-ci/archive/20220329/[email protected]/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
reproduce (this is a W=1 build):
        # https://github.com/ammarfaizi2/linux-block/commit/c3b9dcd01973935375ca9d0c67044bea7333d4ef
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block bp/bp/rc0+
        git checkout c3b9dcd01973935375ca9d0c67044bea7333d4ef
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/kernel/cpu/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>

All errors (new ones prefixed by >>):

   arch/x86/kernel/cpu/common.c: In function 'cpu_parse_early_param':
>> arch/x86/kernel/cpu/common.c:1415:10: error: 'x86_cap_flags' undeclared (first use in this function); did you mean 'x86_cap_flag'?
    1415 |     if (!x86_cap_flags[bit])
         |          ^~~~~~~~~~~~~
         |          x86_cap_flag
   arch/x86/kernel/cpu/common.c:1415:10: note: each undeclared identifier is reported only once for each function it appears in


vim +1415 arch/x86/kernel/cpu/common.c

  1385	
  1386		if (cmdline_find_option_bool(boot_command_line, "noxsave"))
  1387			setup_clear_cpu_cap(X86_FEATURE_XSAVE);
  1388	
  1389		if (cmdline_find_option_bool(boot_command_line, "noxsaveopt"))
  1390			setup_clear_cpu_cap(X86_FEATURE_XSAVEOPT);
  1391	
  1392		if (cmdline_find_option_bool(boot_command_line, "noxsaves"))
  1393			setup_clear_cpu_cap(X86_FEATURE_XSAVES);
  1394	
  1395		arglen = cmdline_find_option(boot_command_line, "clearcpuid", arg, sizeof(arg));
  1396		if (arglen <= 0)
  1397			return;
  1398	
  1399		pr_info("Clearing CPUID bits:");
  1400	
  1401		while (argptr) {
  1402			bool found __maybe_unused = false;
  1403			unsigned int bit;
  1404	
  1405			opt = strsep(&argptr, ",");
  1406	
  1407			/*
  1408			 * Handle naked numbers first for feature flags which don't
  1409			 * have names.
  1410			 */
  1411			if (!kstrtouint(opt, 10, &bit)) {
  1412				if (bit < NCAPINTS * 32) {
  1413	
  1414					/* empty-string, i.e., ""-defined feature flags */
> 1415					if (!x86_cap_flags[bit])
  1416						pr_cont(" " X86_CAP_FMT_NUM, x86_cap_flag_num(bit));
  1417					else
  1418						pr_cont(" " X86_CAP_FMT, x86_cap_flag(bit));
  1419	
  1420					setup_clear_cpu_cap(bit);
  1421					taint++;
  1422				}
  1423				/*
  1424				 * The assumption is that there are no feature names with only
  1425				 * numbers in the name thus go to the next argument.
  1426				 */
  1427				continue;
  1428			}
  1429	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

             reply	other threads:[~2022-03-29 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 14:23 kernel test robot [this message]
2022-03-30 10:23 ` [ammarfaizi2-block:bp/bp/rc0+ 6/11] arch/x86/kernel/cpu/common.c:1415:10: error: 'x86_cap_flags' undeclared; did you mean 'x86_cap_flag'? Borislav Petkov

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox