From: kernel test robot <lkp@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [broonie-ci:arm64-gcs 5/9] arch/arm64/include/asm/kvm_nested.h:281:3: error: use of undeclared identifier 'elr'
Date: Sat, 18 Jul 2026 10:33:13 +0800 [thread overview]
Message-ID: <202607180927.HAmB6swe-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git arm64-gcs
head: a26aa760586e73f8bb0a6cf67438ad0d89c486f5
commit: b2c35cdee47a019777aa9f9216b49a6392cc79e3 [5/9] KVM: arm64: Validate GCS exception lock when emulating ERET
config: arm64-randconfig-004-20260718 (https://download.01.org/0day-ci/archive/20260718/202607180927.HAmB6swe-lkp@intel.com/config)
compiler: clang version 21.1.8 (https://github.com/llvm/llvm-project 2078da43e25a4623cab2d0d60decddf709aaea28)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260718/202607180927.HAmB6swe-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/202607180927.HAmB6swe-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/arm64/kernel/smp.c:46:
In file included from arch/arm64/include/asm/kvm_mmu.h:99:
In file included from arch/arm64/include/asm/kvm_emulate.h:21:
>> arch/arm64/include/asm/kvm_nested.h:281:3: error: use of undeclared identifier 'elr'
281 | *elr = 0xbad9acc0debadbad;
| ^~~
1 error generated.
vim +/elr +281 arch/arm64/include/asm/kvm_nested.h
274
275 #else
276 static inline bool kvm_check_illegal_exlock_return(struct kvm_vcpu *vcpu,
277 u64 spsr)
278 {
279 /* We really should never execute this... */
280 WARN_ON_ONCE(1);
> 281 *elr = 0xbad9acc0debadbad;
282 return false;
283 }
284 #endif
285
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-18 2:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607180927.HAmB6swe-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox