From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: arch/arm64/kvm/hyp/nvhe/mem_protect.c:26:17: sparse: sparse: symbol 'host_s2_mem' was not declared. Should it be static?
Date: Fri, 14 May 2021 08:01:02 +0800 [thread overview]
Message-ID: <202105140846.p2PgYHbZ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]
Hi Stephen,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 315d99318179b9cd5077ccc9f7f26a164c9fa998
commit: 3b7e56be786462423802ff84525b9a12539c5887 Merge branch 'kvm-arm64/nvhe-sve' into kvmarm-master/next
date: 4 weeks ago
config: arm64-randconfig-s032-20210513 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b7e56be786462423802ff84525b9a12539c5887
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 3b7e56be786462423802ff84525b9a12539c5887
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/hyp/nvhe/mem_protect.c:26:17: sparse: sparse: symbol 'host_s2_mem' was not declared. Should it be static?
>> arch/arm64/kvm/hyp/nvhe/mem_protect.c:27:17: sparse: sparse: symbol 'host_s2_dev' was not declared. Should it be static?
vim +/host_s2_mem +26 arch/arm64/kvm/hyp/nvhe/mem_protect.c
1025c8c0c6accf Quentin Perret 2021-03-19 25
1025c8c0c6accf Quentin Perret 2021-03-19 @26 struct hyp_pool host_s2_mem;
1025c8c0c6accf Quentin Perret 2021-03-19 @27 struct hyp_pool host_s2_dev;
1025c8c0c6accf Quentin Perret 2021-03-19 28
:::::: The code at line 26 was first introduced by commit
:::::: 1025c8c0c6accfcbdc8f52ca1940160f65cd87d6 KVM: arm64: Wrap the host with a stage 2
:::::: TO: Quentin Perret <qperret@google.com>
:::::: CC: Marc Zyngier <maz@kernel.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 43920 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: arch/arm64/kvm/hyp/nvhe/mem_protect.c:26:17: sparse: sparse: symbol 'host_s2_mem' was not declared. Should it be static?
Date: Fri, 14 May 2021 08:01:02 +0800 [thread overview]
Message-ID: <202105140846.p2PgYHbZ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
Hi Stephen,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 315d99318179b9cd5077ccc9f7f26a164c9fa998
commit: 3b7e56be786462423802ff84525b9a12539c5887 Merge branch 'kvm-arm64/nvhe-sve' into kvmarm-master/next
date: 4 weeks ago
config: arm64-randconfig-s032-20210513 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b7e56be786462423802ff84525b9a12539c5887
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 3b7e56be786462423802ff84525b9a12539c5887
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/hyp/nvhe/mem_protect.c:26:17: sparse: sparse: symbol 'host_s2_mem' was not declared. Should it be static?
>> arch/arm64/kvm/hyp/nvhe/mem_protect.c:27:17: sparse: sparse: symbol 'host_s2_dev' was not declared. Should it be static?
vim +/host_s2_mem +26 arch/arm64/kvm/hyp/nvhe/mem_protect.c
1025c8c0c6accf Quentin Perret 2021-03-19 25
1025c8c0c6accf Quentin Perret 2021-03-19 @26 struct hyp_pool host_s2_mem;
1025c8c0c6accf Quentin Perret 2021-03-19 @27 struct hyp_pool host_s2_dev;
1025c8c0c6accf Quentin Perret 2021-03-19 28
:::::: The code at line 26 was first introduced by commit
:::::: 1025c8c0c6accfcbdc8f52ca1940160f65cd87d6 KVM: arm64: Wrap the host with a stage 2
:::::: TO: Quentin Perret <qperret@google.com>
:::::: CC: Marc Zyngier <maz@kernel.org>
---
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: 43920 bytes --]
next reply other threads:[~2021-05-14 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 0:01 kernel test robot [this message]
2021-05-14 0:01 ` arch/arm64/kvm/hyp/nvhe/mem_protect.c:26:17: sparse: sparse: symbol 'host_s2_mem' was not declared. Should it be static? kernel test robot
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=202105140846.p2PgYHbZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.