From: kernel test robot <lkp@intel.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC 2/2] cpu/bugs: cgroup: Add a cgroup knob to bypass CPU mitigations
Date: Sat, 21 Sep 2024 13:36:44 +0800 [thread overview]
Message-ID: <202409211355.QTGhbQvW-lkp@intel.com> (raw)
In-Reply-To: <20240919-selective-mitigation-v1-2-1846cf41895e@linux.intel.com>
Hi Pawan,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on 98f7e32f20d28ec452afb208f9cffc08448a2652]
url: https://github.com/intel-lab-lkp/linux/commits/Pawan-Gupta/x86-entry_64-Add-a-separate-unmitigated-entry-exit-path/20240920-055414
base: 98f7e32f20d28ec452afb208f9cffc08448a2652
patch link: https://lore.kernel.org/r/20240919-selective-mitigation-v1-2-1846cf41895e%40linux.intel.com
patch subject: [PATCH RFC 2/2] cpu/bugs: cgroup: Add a cgroup knob to bypass CPU mitigations
config: i386-defconfig (https://download.01.org/0day-ci/archive/20240921/202409211355.QTGhbQvW-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240921/202409211355.QTGhbQvW-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/202409211355.QTGhbQvW-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kernel/cpu/bugs.c:147:36: error: use of undeclared identifier 'entry_SYSCALL_64_unmitigated'
147 | wrmsrl(MSR_LSTAR, (unsigned long)entry_SYSCALL_64_unmitigated);
| ^
>> arch/x86/kernel/cpu/bugs.c:149:36: error: use of undeclared identifier 'entry_SYSCALL_64_mitigated'
149 | wrmsrl(MSR_LSTAR, (unsigned long)entry_SYSCALL_64_mitigated);
| ^
2 errors generated.
vim +/entry_SYSCALL_64_unmitigated +147 arch/x86/kernel/cpu/bugs.c
130
131 inline void cpu_mitigation_skip(struct task_struct *prev,
132 struct task_struct *next)
133 {
134 bool prev_skip = false, next_skip = false;
135
136 if (prev->mm)
137 prev_skip = task_dfl_cgroup(prev)->cpu_skip_mitigation;
138 if (next->mm)
139 next_skip = task_dfl_cgroup(next)->cpu_skip_mitigation;
140
141 if (!prev_skip && !next_skip)
142 return;
143 if (prev_skip == next_skip)
144 return;
145
146 if (next_skip)
> 147 wrmsrl(MSR_LSTAR, (unsigned long)entry_SYSCALL_64_unmitigated);
148 else
> 149 wrmsrl(MSR_LSTAR, (unsigned long)entry_SYSCALL_64_mitigated);
150 }
151
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-09-21 5:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240919-selective-mitigation-v1-2-1846cf41895e@linux.intel.com>]
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=202409211355.QTGhbQvW-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawan.kumar.gupta@linux.intel.com \
/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