From: kbuild test robot <lkp@intel.com>
To: Jiri Bohac <jbohac@suse.cz>
Cc: kbuild-all@01.org, linux-security-module@vger.kernel.org,
James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
Matthew Garrett <mjg59@google.com>,
Dave Young <dyoung@redhat.com>
Subject: [security:next-lockdown 8/29] arch/s390/kernel/kexec_elf.c:134:3: error: 'const struct kexec_file_ops' has no member named 'verify_sig'
Date: Sat, 10 Aug 2019 16:27:44 +0800 [thread overview]
Message-ID: <201908101640.PITi8vxK%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2790 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/jmorris/linux-security.git next-lockdown
head: 05ef41e93e1a40d6b2d9846284824ec6f67fe422
commit: 47b888368923ec6ccd96c6a654250867def4a2c4 [8/29] kexec_file: split KEXEC_VERIFY_SIG into KEXEC_SIG and KEXEC_SIG_FORCE
config: s390-allmodconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 47b888368923ec6ccd96c6a654250867def4a2c4
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=s390
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> arch/s390/kernel/kexec_elf.c:134:3: error: 'const struct kexec_file_ops' has no member named 'verify_sig'
.verify_sig = s390_verify_sig,
^~~~~~~~~~
>> arch/s390/kernel/kexec_elf.c:134:16: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
.verify_sig = s390_verify_sig,
^~~~~~~~~~~~~~~
arch/s390/kernel/kexec_elf.c:134:16: note: (near initialization for 's390_kexec_elf_ops')
cc1: some warnings being treated as errors
--
>> arch/s390/kernel/kexec_image.c:63:3: error: 'const struct kexec_file_ops' has no member named 'verify_sig'
.verify_sig = s390_verify_sig,
^~~~~~~~~~
>> arch/s390/kernel/kexec_image.c:63:16: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
.verify_sig = s390_verify_sig,
^~~~~~~~~~~~~~~
arch/s390/kernel/kexec_image.c:63:16: note: (near initialization for 's390_kexec_image_ops')
cc1: some warnings being treated as errors
vim +134 arch/s390/kernel/kexec_elf.c
8be01882715466 Philipp Rudo 2017-09-11 129
8be01882715466 Philipp Rudo 2017-09-11 130 const struct kexec_file_ops s390_kexec_elf_ops = {
8be01882715466 Philipp Rudo 2017-09-11 131 .probe = s390_elf_probe,
8be01882715466 Philipp Rudo 2017-09-11 132 .load = s390_elf_load,
e23a8020ce4e09 Philipp Rudo 2019-02-26 133 #ifdef CONFIG_KEXEC_VERIFY_SIG
e23a8020ce4e09 Philipp Rudo 2019-02-26 @134 .verify_sig = s390_verify_sig,
:::::: The code at line 134 was first introduced by commit
:::::: e23a8020ce4e094e10d717d39a8ce799243bf8c1 s390/kexec_file: Signature verification prototype
:::::: TO: Philipp Rudo <prudo@linux.ibm.com>
:::::: CC: Martin Schwidefsky <schwidefsky@de.ibm.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 55330 bytes --]
reply other threads:[~2019-08-10 8:28 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=201908101640.PITi8vxK%lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=dyoung@redhat.com \
--cc=jbohac@suse.cz \
--cc=jmorris@namei.org \
--cc=kbuild-all@01.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.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;
as well as URLs for NNTP newsgroup(s).