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-store-gcscre0 6/6] arch/arm64/kernel/signal.c:753:22: error: no member named 'gcs_el0_mode' in 'struct thread_struct'; did you mean 'gcs_el0_locked'?
Date: Thu, 15 Oct 2026 07:18:54 +0200 [thread overview]
Message-ID: <202610150747.IICDPmuf-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git arm64-gcs-store-gcscre0
head: 7f99cf9ccec2ef02e83b4cef2449ee2a931448cd
commit: 7f99cf9ccec2ef02e83b4cef2449ee2a931448cd [6/6] arm64/gcs: Store GCSCRE0_EL1 values instead of userspace mode
config: arm64-randconfig-2001-20261015 (https://download.01.org/0day-ci/archive/20261015/202610150747.IICDPmuf-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261015/202610150747.IICDPmuf-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/202610150747.IICDPmuf-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/arm64/kernel/signal.c:753:22: error: no member named 'gcs_el0_mode' in 'struct thread_struct'; did you mean 'gcs_el0_locked'?
753 | if (current->thread.gcs_el0_mode != enabled)
| ^~~~~~~~~~~~
| gcs_el0_locked
arch/arm64/include/asm/processor.h:200:16: note: 'gcs_el0_locked' declared here
200 | unsigned int gcs_el0_locked;
| ^
1 error generated.
vim +753 arch/arm64/kernel/signal.c
16f47bb9ac8afe0 Mark Brown 2024-10-01 735
16f47bb9ac8afe0 Mark Brown 2024-10-01 736 static int restore_gcs_context(struct user_ctxs *user)
16f47bb9ac8afe0 Mark Brown 2024-10-01 737 {
16f47bb9ac8afe0 Mark Brown 2024-10-01 738 u64 gcspr, enabled;
16f47bb9ac8afe0 Mark Brown 2024-10-01 739 int err = 0;
16f47bb9ac8afe0 Mark Brown 2024-10-01 740
16f47bb9ac8afe0 Mark Brown 2024-10-01 741 if (user->gcs_size != sizeof(*user->gcs))
16f47bb9ac8afe0 Mark Brown 2024-10-01 742 return -EINVAL;
16f47bb9ac8afe0 Mark Brown 2024-10-01 743
16f47bb9ac8afe0 Mark Brown 2024-10-01 744 __get_user_error(gcspr, &user->gcs->gcspr, err);
16f47bb9ac8afe0 Mark Brown 2024-10-01 745 __get_user_error(enabled, &user->gcs->features_enabled, err);
16f47bb9ac8afe0 Mark Brown 2024-10-01 746 if (err)
16f47bb9ac8afe0 Mark Brown 2024-10-01 747 return err;
16f47bb9ac8afe0 Mark Brown 2024-10-01 748
eab95b122151dce Mark Brown 2026-10-14 749 /*
eab95b122151dce Mark Brown 2026-10-14 750 * Don't allow any mode changes, the signal handler should use
eab95b122151dce Mark Brown 2026-10-14 751 * pcrtl() to disable if it wants to do that.
eab95b122151dce Mark Brown 2026-10-14 752 */
eab95b122151dce Mark Brown 2026-10-14 @753 if (current->thread.gcs_el0_mode != enabled)
16f47bb9ac8afe0 Mark Brown 2024-10-01 754 return -EINVAL;
16f47bb9ac8afe0 Mark Brown 2024-10-01 755
16f47bb9ac8afe0 Mark Brown 2024-10-01 756 /*
16f47bb9ac8afe0 Mark Brown 2024-10-01 757 * We let userspace set GCSPR_EL0 to anything here, we will
16f47bb9ac8afe0 Mark Brown 2024-10-01 758 * validate later in gcs_restore_signal().
16f47bb9ac8afe0 Mark Brown 2024-10-01 759 */
16f47bb9ac8afe0 Mark Brown 2024-10-01 760 write_sysreg_s(gcspr, SYS_GCSPR_EL0);
16f47bb9ac8afe0 Mark Brown 2024-10-01 761
16f47bb9ac8afe0 Mark Brown 2024-10-01 762 return 0;
16f47bb9ac8afe0 Mark Brown 2024-10-01 763 }
16f47bb9ac8afe0 Mark Brown 2024-10-01 764
:::::: The code at line 753 was first introduced by commit
:::::: eab95b122151dce193998db2f05cab3a4b79ceed arm64/gcs: Don't allow any GCS mode changes in signal return
:::::: TO: Mark Brown <broonie@kernel.org>
:::::: CC: Mark Brown <broonie@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-15 5:19 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=202610150747.IICDPmuf-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 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.