From: kernel test robot <lkp@intel.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
x86@kernel.org, David Kaplan <david.kaplan@amd.com>,
Nikolay Borisov <nik.borisov@suse.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Asit Mallick <asit.k.mallick@intel.com>,
Tao Zhang <tao1.zhang@intel.com>
Subject: Re: [PATCH v5 4/9] x86/vmscape: Move mitigation selection to a switch()
Date: Thu, 27 Nov 2025 09:04:41 +0800 [thread overview]
Message-ID: <202511270829.xMEXUXCW-lkp@intel.com> (raw)
In-Reply-To: <20251126-vmscape-bhb-v5-4-02d66e423b00@linux.intel.com>
Hi Pawan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 6a23ae0a96a600d1d12557add110e0bb6e32730c]
url: https://github.com/intel-lab-lkp/linux/commits/Pawan-Gupta/x86-bhi-x86-vmscape-Move-LFENCE-out-of-clear_bhb_loop/20251127-061843
base: 6a23ae0a96a600d1d12557add110e0bb6e32730c
patch link: https://lore.kernel.org/r/20251126-vmscape-bhb-v5-4-02d66e423b00%40linux.intel.com
patch subject: [PATCH v5 4/9] x86/vmscape: Move mitigation selection to a switch()
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20251127/202511270829.xMEXUXCW-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251127/202511270829.xMEXUXCW-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/202511270829.xMEXUXCW-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/cpu/bugs.c:3260:2: warning: label at end of compound statement is a C23 extension [-Wc23-extensions]
3260 | }
| ^
1 warning generated.
vim +3260 arch/x86/kernel/cpu/bugs.c
556c1ad666ad90 Pawan Gupta 2025-08-14 3231
556c1ad666ad90 Pawan Gupta 2025-08-14 3232 static void __init vmscape_select_mitigation(void)
556c1ad666ad90 Pawan Gupta 2025-08-14 3233 {
0091dd36e9ee51 Pawan Gupta 2025-11-26 3234 if (!boot_cpu_has_bug(X86_BUG_VMSCAPE)) {
556c1ad666ad90 Pawan Gupta 2025-08-14 3235 vmscape_mitigation = VMSCAPE_MITIGATION_NONE;
556c1ad666ad90 Pawan Gupta 2025-08-14 3236 return;
556c1ad666ad90 Pawan Gupta 2025-08-14 3237 }
556c1ad666ad90 Pawan Gupta 2025-08-14 3238
0091dd36e9ee51 Pawan Gupta 2025-11-26 3239 if ((vmscape_mitigation == VMSCAPE_MITIGATION_AUTO) &&
0091dd36e9ee51 Pawan Gupta 2025-11-26 3240 !should_mitigate_vuln(X86_BUG_VMSCAPE))
0091dd36e9ee51 Pawan Gupta 2025-11-26 3241 vmscape_mitigation = VMSCAPE_MITIGATION_NONE;
0091dd36e9ee51 Pawan Gupta 2025-11-26 3242
0091dd36e9ee51 Pawan Gupta 2025-11-26 3243 switch (vmscape_mitigation) {
0091dd36e9ee51 Pawan Gupta 2025-11-26 3244 case VMSCAPE_MITIGATION_NONE:
0091dd36e9ee51 Pawan Gupta 2025-11-26 3245 break;
0091dd36e9ee51 Pawan Gupta 2025-11-26 3246
0091dd36e9ee51 Pawan Gupta 2025-11-26 3247 case VMSCAPE_MITIGATION_IBPB_EXIT_TO_USER:
0091dd36e9ee51 Pawan Gupta 2025-11-26 3248 if (!boot_cpu_has(X86_FEATURE_IBPB))
0091dd36e9ee51 Pawan Gupta 2025-11-26 3249 vmscape_mitigation = VMSCAPE_MITIGATION_NONE;
0091dd36e9ee51 Pawan Gupta 2025-11-26 3250 break;
0091dd36e9ee51 Pawan Gupta 2025-11-26 3251
0091dd36e9ee51 Pawan Gupta 2025-11-26 3252 case VMSCAPE_MITIGATION_AUTO:
0091dd36e9ee51 Pawan Gupta 2025-11-26 3253 if (boot_cpu_has(X86_FEATURE_IBPB))
556c1ad666ad90 Pawan Gupta 2025-08-14 3254 vmscape_mitigation = VMSCAPE_MITIGATION_IBPB_EXIT_TO_USER;
5799d5d8a6c877 David Kaplan 2025-09-12 3255 else
5799d5d8a6c877 David Kaplan 2025-09-12 3256 vmscape_mitigation = VMSCAPE_MITIGATION_NONE;
0091dd36e9ee51 Pawan Gupta 2025-11-26 3257 break;
0091dd36e9ee51 Pawan Gupta 2025-11-26 3258
0091dd36e9ee51 Pawan Gupta 2025-11-26 3259 default:
5799d5d8a6c877 David Kaplan 2025-09-12 @3260 }
556c1ad666ad90 Pawan Gupta 2025-08-14 3261 }
556c1ad666ad90 Pawan Gupta 2025-08-14 3262
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-27 1:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 22:14 [PATCH v5 0/9] VMSCAPE optimization for BHI variant Pawan Gupta
2025-11-26 22:14 ` [PATCH v5 1/9] x86/bhi: x86/vmscape: Move LFENCE out of clear_bhb_loop() Pawan Gupta
2025-11-26 22:15 ` [PATCH v5 2/9] x86/bhi: Make clear_bhb_loop() effective on newer CPUs Pawan Gupta
2025-11-26 22:15 ` [PATCH v5 3/9] x86/vmscape: Rename x86_ibpb_exit_to_user to x86_predictor_flush_exit_to_user Pawan Gupta
2025-11-26 22:15 ` [PATCH v5 4/9] x86/vmscape: Move mitigation selection to a switch() Pawan Gupta
2025-11-27 1:04 ` kernel test robot [this message]
2025-11-29 19:35 ` kernel test robot
2025-11-26 22:15 ` [PATCH v5 5/9] x86/vmscape: Use write_ibpb() instead of indirect_branch_prediction_barrier() Pawan Gupta
2025-11-26 22:16 ` [PATCH v5 6/9] x86/vmscape: Use static_call() for predictor flush Pawan Gupta
2025-11-26 22:16 ` [PATCH v5 7/9] x86/vmscape: Deploy BHB clearing mitigation Pawan Gupta
2025-11-26 22:16 ` [PATCH v5 8/9] x86/vmscape: Fix conflicting attack-vector controls with =force Pawan Gupta
2025-11-26 22:16 ` [PATCH v5 9/9] x86/vmscape: Add cmdline vmscape=on to override attack vector controls Pawan Gupta
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=202511270829.xMEXUXCW-lkp@intel.com \
--to=lkp@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nik.borisov@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tao1.zhang@intel.com \
--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 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.