From: kbuild test robot <lkp@intel.com>
To: Thiago Jung Bauermann <bauerman@linux.ibm.com>
Cc: kbuild-all@01.org, linux-integrity@vger.kernel.org,
Mimi Zohar <zohar@linux.ibm.com>
Subject: [integrity:next-queued-testing 2/13] include/linux/module_signature.h:32:2: error: unknown type name 'u8'
Date: Thu, 8 Aug 2019 07:00:55 +0800 [thread overview]
Message-ID: <201908080752.5U4CXtOx%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2803 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-queued-testing
head: cd3553a6a5047b7a759803ae3ba3991a901b89f8
commit: a5e7fd15c3b94862ce3639e82cabd2de74a0ad90 [2/13] MODSIGN: Export module signature definitions
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
git checkout a5e7fd15c3b94862ce3639e82cabd2de74a0ad90
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:0:0:
>> include/linux/module_signature.h:32:2: error: unknown type name 'u8'
u8 algo; /* Public-key crypto algorithm [0] */
^~
include/linux/module_signature.h:33:2: error: unknown type name 'u8'
u8 hash; /* Digest algorithm [0] */
^~
include/linux/module_signature.h:34:2: error: unknown type name 'u8'
u8 id_type; /* Key identifier type [PKEY_ID_PKCS7] */
^~
include/linux/module_signature.h:35:2: error: unknown type name 'u8'
u8 signer_len; /* Length of signer's name [0] */
^~
include/linux/module_signature.h:36:2: error: unknown type name 'u8'
u8 key_id_len; /* Length of key identifier [0] */
^~
include/linux/module_signature.h:37:2: error: unknown type name 'u8'
u8 __pad[3];
^~
>> include/linux/module_signature.h:38:2: error: unknown type name '__be32'
__be32 sig_len; /* Length of signature data */
^~~~~~
>> include/linux/module_signature.h:41:54: error: unknown type name 'size_t'
int mod_check_sig(const struct module_signature *ms, size_t file_len,
^~~~~~
vim +/u8 +32 include/linux/module_signature.h
20
21 /*
22 * Module signature information block.
23 *
24 * The constituents of the signature section are, in order:
25 *
26 * - Signer's name
27 * - Key identifier
28 * - Signature data
29 * - Information block
30 */
31 struct module_signature {
> 32 u8 algo; /* Public-key crypto algorithm [0] */
33 u8 hash; /* Digest algorithm [0] */
34 u8 id_type; /* Key identifier type [PKEY_ID_PKCS7] */
> 35 u8 signer_len; /* Length of signer's name [0] */
> 36 u8 key_id_len; /* Length of key identifier [0] */
37 u8 __pad[3];
> 38 __be32 sig_len; /* Length of signature data */
39 };
40
> 41 int mod_check_sig(const struct module_signature *ms, size_t file_len,
42 const char *name);
43
---
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: 69526 bytes --]
next reply other threads:[~2019-08-07 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 23:00 kbuild test robot [this message]
2019-08-08 0:55 ` [integrity:next-queued-testing 2/13] include/linux/module_signature.h:32:2: error: unknown type name 'u8' Thiago Jung Bauermann
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=201908080752.5U4CXtOx%lkp@intel.com \
--to=lkp@intel.com \
--cc=bauerman@linux.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-integrity@vger.kernel.org \
--cc=zohar@linux.ibm.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