From: kernel test robot <lkp@intel.com>
To: Will Deacon <will@kernel.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 3528/7280] arch/arm64/include/asm/probes.h:16:2: error: unknown type name 'pstate_check_t'
Date: Fri, 20 Nov 2020 21:24:56 +0800 [thread overview]
Message-ID: <202011202153.eV1kqtnz-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3022 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 95065cb54210eba86bed10cb2118041524d54573
commit: 7cda23da52ad793a578d290e7fcc9cdc1698bba8 [3528/7280] arm64: alternatives: Split up alternative.h
config: arm64-randconfig-p002-20201120 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=7cda23da52ad793a578d290e7fcc9cdc1698bba8
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 7cda23da52ad793a578d290e7fcc9cdc1698bba8
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from arch/arm64/include/asm/kprobes.h:24,
from arch/arm64/include/asm/exception.h:11,
from arch/arm64/kernel/fpsimd.c:35:
>> arch/arm64/include/asm/probes.h:16:2: error: unknown type name 'pstate_check_t'
16 | pstate_check_t *pstate_cc;
| ^~~~~~~~~~~~~~
vim +/pstate_check_t +16 arch/arm64/include/asm/probes.h
2dd0e8d2d2a157d Sandeepa Prabhu 2016-07-08 12
2dd0e8d2d2a157d Sandeepa Prabhu 2016-07-08 13 /* architecture specific copy of original instruction */
c2249707ee53b5d Pratyush Anand 2016-11-02 14 struct arch_probe_insn {
c2249707ee53b5d Pratyush Anand 2016-11-02 15 probe_opcode_t *insn;
39a67d49ba35363 Sandeepa Prabhu 2016-07-08 @16 pstate_check_t *pstate_cc;
c2249707ee53b5d Pratyush Anand 2016-11-02 17 probes_handler_t *handler;
2dd0e8d2d2a157d Sandeepa Prabhu 2016-07-08 18 /* restore address after step xol */
2dd0e8d2d2a157d Sandeepa Prabhu 2016-07-08 19 unsigned long restore;
2dd0e8d2d2a157d Sandeepa Prabhu 2016-07-08 20 };
c2249707ee53b5d Pratyush Anand 2016-11-02 21 #ifdef CONFIG_KPROBES
c2249707ee53b5d Pratyush Anand 2016-11-02 22 typedef u32 kprobe_opcode_t;
c2249707ee53b5d Pratyush Anand 2016-11-02 23 struct arch_specific_insn {
c2249707ee53b5d Pratyush Anand 2016-11-02 24 struct arch_probe_insn api;
c2249707ee53b5d Pratyush Anand 2016-11-02 25 };
c2249707ee53b5d Pratyush Anand 2016-11-02 26 #endif
2dd0e8d2d2a157d Sandeepa Prabhu 2016-07-08 27
:::::: The code at line 16 was first introduced by commit
:::::: 39a67d49ba353630d144a8eb775500c041c89e7a arm64: kprobes instruction simulation support
:::::: TO: Sandeepa Prabhu <sandeepa.s.prabhu@gmail.com>
:::::: CC: Catalin Marinas <catalin.marinas@arm.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37614 bytes --]
reply other threads:[~2020-11-20 13:25 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=202011202153.eV1kqtnz-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).