Re: [integrity:next-queued-testing 2/13] include/linux/module_signature.h:32:2: error: unknown type name 'u8'

[Thiago Jung Bauermann <bauerman@linux.ibm.com>]

kbuild test robot <lkp@intel.com> writes:

> 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,
>                                                          ^~~~~~

This is the same issue spotted and fixed by Stephen Rothwell here:

https://lore.kernel.org/linux-next/20190806121519.0f8ac653@canb.auug.org.au/

Mimi added his patch to her linux-integrity/next-integrity branch so it
is fixed already.
-- 
Thiago Jung Bauermann
IBM Linux Technology Center