From: kernel test robot <lkp@intel.com>
To: David Kaplan <david.kaplan@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Brendan Jackman <jackmanb@google.com>,
Derek Manwaring <derekmn@amazon.com>
Subject: Re: [PATCH v4 20/36] x86/bugs: Determine relevant vulnerabilities based on attack vector controls.
Date: Wed, 12 Mar 2025 19:32:07 +0800 [thread overview]
Message-ID: <202503121906.IF0k61bY-lkp@intel.com> (raw)
In-Reply-To: <20250310164023.779191-21-david.kaplan@amd.com>
Hi David,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/master]
[cannot apply to tip/x86/core linus/master tip/auto-latest tip/smp/core v6.14-rc6 next-20250311]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/David-Kaplan/x86-bugs-Restructure-mds-mitigation/20250311-005151
base: tip/master
patch link: https://lore.kernel.org/r/20250310164023.779191-21-david.kaplan%40amd.com
patch subject: [PATCH v4 20/36] x86/bugs: Determine relevant vulnerabilities based on attack vector controls.
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20250312/202503121906.IF0k61bY-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250312/202503121906.IF0k61bY-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/202503121906.IF0k61bY-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kernel/cpu/bugs.c:351:11: error: use of undeclared identifier 'smt_mitigations'; did you mean 'l1tf_mitigation'?
351 | (smt_mitigations != SMT_MITIGATIONS_OFF);
| ^~~~~~~~~~~~~~~
| l1tf_mitigation
arch/x86/include/asm/processor.h:745:30: note: 'l1tf_mitigation' declared here
745 | extern enum l1tf_mitigations l1tf_mitigation;
| ^
arch/x86/kernel/cpu/bugs.c:1561:7: warning: variable 'smt_possible' set but not used [-Wunused-but-set-variable]
1561 | bool smt_possible = IS_ENABLED(CONFIG_SMP);
| ^
1 warning and 1 error generated.
vim +351 arch/x86/kernel/cpu/bugs.c
302
303 /*
304 * Returns true if vulnerability should be mitigated based on the
305 * selected attack vector controls.
306 *
307 * See Documentation/admin-guide/hw-vuln/attack_vector_controls.rst
308 */
309 static bool __init should_mitigate_vuln(unsigned int bug)
310 {
311 switch (bug) {
312 /*
313 * The only runtime-selected spectre_v1 mitigations in the kernel are
314 * related to SWAPGS protection on kernel entry. Therefore, protection
315 * is only required for the user->kernel attack vector.
316 */
317 case X86_BUG_SPECTRE_V1:
318 return cpu_mitigate_attack_vector(CPU_MITIGATE_USER_KERNEL);
319
320 case X86_BUG_SPECTRE_V2:
321 case X86_BUG_RETBLEED:
322 case X86_BUG_SRSO:
323 case X86_BUG_L1TF:
324 return cpu_mitigate_attack_vector(CPU_MITIGATE_USER_KERNEL) ||
325 cpu_mitigate_attack_vector(CPU_MITIGATE_GUEST_HOST);
326
327 case X86_BUG_SPECTRE_V2_USER:
328 return cpu_mitigate_attack_vector(CPU_MITIGATE_USER_USER) ||
329 cpu_mitigate_attack_vector(CPU_MITIGATE_GUEST_GUEST);
330
331 /*
332 * All the vulnerabilities below allow potentially leaking data
333 * across address spaces. Therefore, mitigation is required for
334 * any of these 4 attack vectors.
335 */
336 case X86_BUG_MDS:
337 case X86_BUG_TAA:
338 case X86_BUG_MMIO_STALE_DATA:
339 case X86_BUG_RFDS:
340 case X86_BUG_SRBDS:
341 return cpu_mitigate_attack_vector(CPU_MITIGATE_USER_KERNEL) ||
342 cpu_mitigate_attack_vector(CPU_MITIGATE_GUEST_HOST) ||
343 cpu_mitigate_attack_vector(CPU_MITIGATE_USER_USER) ||
344 cpu_mitigate_attack_vector(CPU_MITIGATE_GUEST_GUEST);
345
346 case X86_BUG_GDS:
347 return cpu_mitigate_attack_vector(CPU_MITIGATE_USER_KERNEL) ||
348 cpu_mitigate_attack_vector(CPU_MITIGATE_GUEST_HOST) ||
349 cpu_mitigate_attack_vector(CPU_MITIGATE_USER_USER) ||
350 cpu_mitigate_attack_vector(CPU_MITIGATE_GUEST_GUEST) ||
> 351 (smt_mitigations != SMT_MITIGATIONS_OFF);
352 default:
353 WARN(1, "Unknown bug %x\n", bug);
354 return false;
355 }
356 }
357
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-12 11:32 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 16:39 [PATCH v4 00/36] Attack " David Kaplan
2025-03-10 16:39 ` [PATCH v4 01/36] x86/bugs: Restructure mds mitigation David Kaplan
2025-03-10 16:39 ` [PATCH v4 02/36] x86/bugs: Restructure taa mitigation David Kaplan
2025-03-10 16:39 ` [PATCH v4 03/36] x86/bugs: Restructure mmio mitigation David Kaplan
2025-03-13 9:36 ` Borislav Petkov
2025-03-13 14:19 ` Kaplan, David
2025-03-13 19:26 ` Pawan Gupta
2025-03-18 14:16 ` MMIO and VERW Borislav Petkov
2025-03-18 16:25 ` Pawan Gupta
2025-03-18 16:34 ` Borislav Petkov
2025-03-18 16:56 ` Pawan Gupta
2025-03-18 17:37 ` Borislav Petkov
2025-03-18 18:15 ` Pawan Gupta
2025-03-18 18:55 ` Borislav Petkov
2025-03-24 9:29 ` [PATCH v4 03/36] x86/bugs: Restructure mmio mitigation Borislav Petkov
2025-03-24 17:41 ` Pawan Gupta
2025-03-25 11:31 ` Borislav Petkov
2025-03-10 16:39 ` [PATCH v4 04/36] x86/bugs: Restructure rfds mitigation David Kaplan
2025-04-10 16:24 ` Josh Poimboeuf
2025-04-14 19:10 ` Kaplan, David
2025-03-10 16:39 ` [PATCH v4 05/36] x86/bugs: Remove md_clear_*_mitigation() David Kaplan
2025-03-10 16:39 ` [PATCH v4 06/36] x86/bugs: Restructure srbds mitigation David Kaplan
2025-03-10 16:39 ` [PATCH v4 07/36] x86/bugs: Restructure gds mitigation David Kaplan
2025-03-10 16:39 ` [PATCH v4 08/36] x86/bugs: Restructure spectre_v1 mitigation David Kaplan
2025-03-10 16:39 ` [PATCH v4 09/36] x86/bugs: Only allow retbleed=stuff on Intel David Kaplan
2025-03-10 16:39 ` [PATCH v4 10/36] x86/bugs: Restructure retbleed mitigation David Kaplan
2025-03-10 16:39 ` [PATCH v4 11/36] x86/bugs: Restructure spectre_v2_user mitigation David Kaplan
2025-03-12 9:49 ` kernel test robot
2025-04-10 16:26 ` Josh Poimboeuf
2025-04-14 19:20 ` Kaplan, David
2025-04-10 16:41 ` Josh Poimboeuf
2025-04-14 19:20 ` Kaplan, David
2025-04-14 23:48 ` Josh Poimboeuf
2025-04-15 14:56 ` Kaplan, David
2025-03-10 16:39 ` [PATCH v4 12/36] x86/bugs: Restructure bhi mitigation David Kaplan
2025-03-10 16:40 ` [PATCH v4 13/36] x86/bugs: Restructure spectre_v2 mitigation David Kaplan
2025-04-10 17:08 ` Josh Poimboeuf
2025-04-14 19:25 ` Kaplan, David
2025-03-10 16:40 ` [PATCH v4 14/36] x86/bugs: Restructure ssb mitigation David Kaplan
2025-03-10 16:40 ` [PATCH v4 15/36] x86/bugs: Restructure l1tf mitigation David Kaplan
2025-03-10 16:40 ` [PATCH v4 16/36] x86/bugs: Restructure srso mitigation David Kaplan
2025-04-10 17:38 ` Josh Poimboeuf
2025-04-14 21:12 ` Kaplan, David
2025-03-10 16:40 ` [PATCH v4 17/36] Documentation/x86: Document the new attack vector controls David Kaplan
2025-04-10 18:14 ` Josh Poimboeuf
2025-04-14 21:15 ` Kaplan, David
2025-04-14 23:51 ` Josh Poimboeuf
2025-04-15 14:59 ` Kaplan, David
2025-04-15 15:32 ` Josh Poimboeuf
2025-04-15 16:10 ` Kaplan, David
2025-04-15 16:47 ` Josh Poimboeuf
2025-04-15 17:06 ` Kaplan, David
2025-03-10 16:40 ` [PATCH v4 18/36] cpu: Define attack vectors David Kaplan
2025-04-10 18:12 ` Josh Poimboeuf
2025-04-14 21:20 ` Kaplan, David
2025-03-10 16:40 ` [PATCH v4 19/36] x86/Kconfig: Arch attack vector support David Kaplan
2025-03-10 16:40 ` [PATCH v4 20/36] x86/bugs: Determine relevant vulnerabilities based on attack vector controls David Kaplan
2025-03-12 11:32 ` kernel test robot [this message]
2025-03-10 16:40 ` [PATCH v4 21/36] x86/bugs: Add attack vector controls for mds David Kaplan
2025-03-10 16:40 ` [PATCH v4 22/36] x86/bugs: Add attack vector controls for taa David Kaplan
2025-03-10 16:40 ` [PATCH v4 23/36] x86/bugs: Add attack vector controls for mmio David Kaplan
2025-03-10 16:40 ` [PATCH v4 24/36] x86/bugs: Add attack vector controls for rfds David Kaplan
2025-03-10 16:40 ` [PATCH v4 25/36] x86/bugs: Add attack vector controls for srbds David Kaplan
2025-03-10 16:40 ` [PATCH v4 26/36] x86/bugs: Add attack vector controls for gds David Kaplan
2025-03-10 16:40 ` [PATCH v4 27/36] x86/bugs: Add attack vector controls for spectre_v1 David Kaplan
2025-03-10 16:40 ` [PATCH v4 28/36] x86/bugs: Add attack vector controls for retbleed David Kaplan
2025-03-10 16:40 ` [PATCH v4 29/36] x86/bugs: Add attack vector controls for spectre_v2_user David Kaplan
2025-03-10 16:40 ` [PATCH v4 30/36] x86/bugs: Add attack vector controls for bhi David Kaplan
2025-03-10 16:40 ` [PATCH v4 31/36] x86/bugs: Add attack vector controls for spectre_v2 David Kaplan
2025-03-10 16:40 ` [PATCH v4 32/36] x86/bugs: Add attack vector controls for l1tf David Kaplan
2025-03-10 16:40 ` [PATCH v4 33/36] x86/bugs: Add attack vector controls for srso David Kaplan
2025-03-10 16:40 ` [PATCH v4 34/36] x86/pti: Add attack vector controls for pti David Kaplan
2025-03-10 16:40 ` [PATCH v4 35/36] x86/bugs: Print enabled attack vectors David Kaplan
2025-03-10 16:40 ` [PATCH v4 36/36] cpu: Show attack vectors in sysfs David Kaplan
2025-03-10 18:45 ` [PATCH v4 00/36] Attack vector controls Ingo Molnar
2025-03-10 20:46 ` Kaplan, David
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=202503121906.IF0k61bY-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=derekmn@amazon.com \
--cc=hpa@zytor.com \
--cc=jackmanb@google.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®