All of lore.kernel.org
 help / color / mirror / Atom feed
* [jarkko-linux-tpmdd:next 9/10] 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem', 'r')
@ 2021-06-23 22:32 kernel test robot
  2021-06-24 15:27 ` Stefan Berger
  0 siblings, 1 reply; 4+ messages in thread
From: kernel test robot @ 2021-06-23 22:32 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

Hi Stefan,

First bad commit (maybe != root cause):

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git next
head:   87e9688481163dee836c7f86e02f9aaf3240af2e
commit: 28d62d945dedd880f9180fbf5361951f126af7b6 [9/10] certs: Trigger creation of RSA module signing key if it's not an RSA key
config: sh-allmodconfig (attached as .config)
compiler: sh4-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/jarkko/linux-tpmdd.git/commit/?id=28d62d945dedd880f9180fbf5361951f126af7b6
        git remote add jarkko-linux-tpmdd git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
        git fetch --no-tags jarkko-linux-tpmdd next
        git checkout 28d62d945dedd880f9180fbf5361951f126af7b6
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sh 

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 >>):

   Can't open certs/signing_key.pem for reading, No such file or directory
>> 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem','r')
>> 140443843548416:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
   unable to load certificate

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_PDC
   Depends on SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC && HAS_DMA
   Selected by
   - SND_ATMEL_SOC_SSC && SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC
   - SND_ATMEL_SOC_SSC_PDC && SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC && ATMEL_SSC

---
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: 54783 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [jarkko-linux-tpmdd:next 9/10] 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem', 'r')
  2021-06-23 22:32 [jarkko-linux-tpmdd:next 9/10] 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem', 'r') kernel test robot
@ 2021-06-24 15:27 ` Stefan Berger
  2021-06-25  8:22   ` Rong Chen
  0 siblings, 1 reply; 4+ messages in thread
From: Stefan Berger @ 2021-06-24 15:27 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 5444 bytes --]

I am at a loss with this. I tried several combinations of openssl and 
key being available/unavailable and they all behave as expected:

With a key available it cross-builds fine for sh:

[...]

   GEN     modules.builtin
   LD      .tmp_vmlinux.kallsyms1
   KSYMS   .tmp_vmlinux.kallsyms1.S
   AS      .tmp_vmlinux.kallsyms1.S
   LD      .tmp_vmlinux.kallsyms2
   KSYMS   .tmp_vmlinux.kallsyms2.S
   AS      .tmp_vmlinux.kallsyms2.S
   LD      vmlinux
   SYSMAP  System.map
   MODPOST modules-only.symvers
ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined!
ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!

ERROR: modpost: "__umoddi3" [fs/btrfs/btrfs.ko] undefined!


With no key available it creates one using the openssl tool.

[...]

Generating a RSA private key
......++++
...................++++
writing new private key to 'certs/signing_key.pem'
-----
###
### Key pair generated.
###
   EXTRACT_CERTS   certs/signing_key.pem
   AS      certs/system_certificates.o
   AR      certs/built-in.a

   CHK     kernel/kheaders_data.tar.xz
   GEN     .version
   CHK     include/generated/compile.h
   UPD     include/generated/compile.h
   CC      init/version.o
   AR      init/built-in.a
   LD      vmlinux.o
   MODPOST vmlinux.symvers
   MODINFO modules.builtin.modinfo
   GEN     modules.builtin

[...]


With a key available and no openssl tool installed it builds fine:

[...]

   GEN     .version
   CHK     include/generated/compile.h
   UPD     include/generated/compile.h
   CC      init/version.o
   AR      init/built-in.a
   LD      vmlinux.o
   MODPOST vmlinux.symvers
   MODINFO modules.builtin.modinfo
   GEN     modules.builtin
   LD      .tmp_vmlinux.kallsyms1
   KSYMS   .tmp_vmlinux.kallsyms1.S
   AS      .tmp_vmlinux.kallsyms1.S
   LD      .tmp_vmlinux.kallsyms2
   KSYMS   .tmp_vmlinux.kallsyms2.S
   AS      .tmp_vmlinux.kallsyms2.S
   LD      vmlinux
   SYSMAP  System.map
   MODPOST modules-only.symvers
ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined!
ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
ERROR: modpost: "__umoddi3" [fs/btrfs/btrfs.ko] undefined!


With no key available and no openssl tool installed it doesn't work. 
This is expected. How should the key be generated? But the error is 
different from what is shown in the original complaint below:


###
### Now generating an X.509 key pair to be used for signing modules.
###
### If this takes a long time, you might wish to run rngd in the
### background to keep the supply of entropy topped up.  It
### needs to be run as root, and uses a hardware random
### number generator if one is available.
###
/bin/sh: openssl: command not found
make[1]: *** [certs/Makefile:82: certs/signing_key.pem] Error 127
make: *** [Makefile:1847: certs] Error 2
make: *** Waiting for unfinished jobs....
   CHK     kernel/kheaders_data.tar.xz


I don't know how to recreate the issue.

   Stefan



On 6/23/21 6:32 PM, kernel test robot wrote:
> Hi Stefan,
>
> First bad commit (maybe != root cause):
>
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git next
> head:   87e9688481163dee836c7f86e02f9aaf3240af2e
> commit: 28d62d945dedd880f9180fbf5361951f126af7b6 [9/10] certs: Trigger creation of RSA module signing key if it's not an RSA key
> config: sh-allmodconfig (attached as .config)
> compiler: sh4-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/jarkko/linux-tpmdd.git/commit/?id=28d62d945dedd880f9180fbf5361951f126af7b6
>          git remote add jarkko-linux-tpmdd git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
>          git fetch --no-tags jarkko-linux-tpmdd next
>          git checkout 28d62d945dedd880f9180fbf5361951f126af7b6
>          # save the attached .config to linux build tree
>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sh
>
> 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 >>):
>
>     Can't open certs/signing_key.pem for reading, No such file or directory
>>> 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem','r')
>>> 140443843548416:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
>     unable to load certificate
>
> Kconfig warnings: (for reference only)
>     WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_PDC
>     Depends on SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC && HAS_DMA
>     Selected by
>     - SND_ATMEL_SOC_SSC && SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC
>     - SND_ATMEL_SOC_SSC_PDC && SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC && ATMEL_SSC
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [jarkko-linux-tpmdd:next 9/10] 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem', 'r')
  2021-06-24 15:27 ` Stefan Berger
@ 2021-06-25  8:22   ` Rong Chen
  2021-06-25 11:58     ` Stefan Berger
  0 siblings, 1 reply; 4+ messages in thread
From: Rong Chen @ 2021-06-25  8:22 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 6937 bytes --]



On 6/24/21 11:27 PM, Stefan Berger wrote:
> I am at a loss with this. I tried several combinations of openssl and 
> key being available/unavailable and they all behave as expected:

Hi Stefan,

I'm not sure what the difference of the test environment, the problem 
can be reproduced in our environment:

make -f ./scripts/Makefile.build obj=certs \
single-build= \
need-builtin=1 need-modorder=1
+ make -f ./scripts/Makefile.build obj=certs single-build= 
need-builtin=1 need-modorder=1
openssl help 2>/dev/null && echo yes
+ openssl help
+ echo yes
openssl x509 -in "certs/signing_key.pem" -text
+ openssl x509 -in certs/signing_key.pem -text
Can't open certs/signing_key.pem for reading, No such file or directory
140403097064704:error:02001002:system library:fopen:No such file or 
directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem','r')
140403097064704:error:2006D080:BIO routines:BIO_new_file:no such 
file:../crypto/bio/bss_file.c:76:
unable to load certificate
rm -f "certs/signing_key.pem"
+ rm -f certs/signing_key.pem

Best Regards,
Rong Chen

>
> With a key available it cross-builds fine for sh:
>
> [...]
>
>   GEN     modules.builtin
>   LD      .tmp_vmlinux.kallsyms1
>   KSYMS   .tmp_vmlinux.kallsyms1.S
>   AS      .tmp_vmlinux.kallsyms1.S
>   LD      .tmp_vmlinux.kallsyms2
>   KSYMS   .tmp_vmlinux.kallsyms2.S
>   AS      .tmp_vmlinux.kallsyms2.S
>   LD      vmlinux
>   SYSMAP  System.map
>   MODPOST modules-only.symvers
> ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined!
> ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
>
> ERROR: modpost: "__umoddi3" [fs/btrfs/btrfs.ko] undefined!
>
>
> With no key available it creates one using the openssl tool.
>
> [...]
>
> Generating a RSA private key
> ......++++
> ...................++++
> writing new private key to 'certs/signing_key.pem'
> -----
> ###
> ### Key pair generated.
> ###
>   EXTRACT_CERTS   certs/signing_key.pem
>   AS      certs/system_certificates.o
>   AR      certs/built-in.a
>
>   CHK     kernel/kheaders_data.tar.xz
>   GEN     .version
>   CHK     include/generated/compile.h
>   UPD     include/generated/compile.h
>   CC      init/version.o
>   AR      init/built-in.a
>   LD      vmlinux.o
>   MODPOST vmlinux.symvers
>   MODINFO modules.builtin.modinfo
>   GEN     modules.builtin
>
> [...]
>
>
> With a key available and no openssl tool installed it builds fine:
>
> [...]
>
>   GEN     .version
>   CHK     include/generated/compile.h
>   UPD     include/generated/compile.h
>   CC      init/version.o
>   AR      init/built-in.a
>   LD      vmlinux.o
>   MODPOST vmlinux.symvers
>   MODINFO modules.builtin.modinfo
>   GEN     modules.builtin
>   LD      .tmp_vmlinux.kallsyms1
>   KSYMS   .tmp_vmlinux.kallsyms1.S
>   AS      .tmp_vmlinux.kallsyms1.S
>   LD      .tmp_vmlinux.kallsyms2
>   KSYMS   .tmp_vmlinux.kallsyms2.S
>   AS      .tmp_vmlinux.kallsyms2.S
>   LD      vmlinux
>   SYSMAP  System.map
>   MODPOST modules-only.symvers
> ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined!
> ERROR: modpost: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
> ERROR: modpost: "__umoddi3" [fs/btrfs/btrfs.ko] undefined!
>
>
> With no key available and no openssl tool installed it doesn't work. 
> This is expected. How should the key be generated? But the error is 
> different from what is shown in the original complaint below:
>
>
> ###
> ### Now generating an X.509 key pair to be used for signing modules.
> ###
> ### If this takes a long time, you might wish to run rngd in the
> ### background to keep the supply of entropy topped up.  It
> ### needs to be run as root, and uses a hardware random
> ### number generator if one is available.
> ###
> /bin/sh: openssl: command not found
> make[1]: *** [certs/Makefile:82: certs/signing_key.pem] Error 127
> make: *** [Makefile:1847: certs] Error 2
> make: *** Waiting for unfinished jobs....
>   CHK     kernel/kheaders_data.tar.xz
>
>
> I don't know how to recreate the issue.
>
>   Stefan
>
>
>
> On 6/23/21 6:32 PM, kernel test robot wrote:
>> Hi Stefan,
>>
>> First bad commit (maybe != root cause):
>>
>> tree: 
>> git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git 
>> next
>> head:   87e9688481163dee836c7f86e02f9aaf3240af2e
>> commit: 28d62d945dedd880f9180fbf5361951f126af7b6 [9/10] certs: 
>> Trigger creation of RSA module signing key if it's not an RSA key
>> config: sh-allmodconfig (attached as .config)
>> compiler: sh4-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/jarkko/linux-tpmdd.git/commit/?id=28d62d945dedd880f9180fbf5361951f126af7b6
>>          git remote add jarkko-linux-tpmdd 
>> git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
>>          git fetch --no-tags jarkko-linux-tpmdd next
>>          git checkout 28d62d945dedd880f9180fbf5361951f126af7b6
>>          # save the attached .config to linux build tree
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 
>> make.cross ARCH=sh
>>
>> 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 >>):
>>
>>     Can't open certs/signing_key.pem for reading, No such file or 
>> directory
>>>> 140443843548416:error:02001002:system library:fopen:No such file or 
>>>> directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem','r') 
>>>>
>>>> 140443843548416:error:2006D080:BIO routines:BIO_new_file:no such 
>>>> file:../crypto/bio/bss_file.c:76:
>>     unable to load certificate
>>
>> Kconfig warnings: (for reference only)
>>     WARNING: unmet direct dependencies detected for SND_ATMEL_SOC_PDC
>>     Depends on SOUND && !UML && SND && SND_SOC && SND_ATMEL_SOC && 
>> HAS_DMA
>>     Selected by
>>     - SND_ATMEL_SOC_SSC && SOUND && !UML && SND && SND_SOC && 
>> SND_ATMEL_SOC
>>     - SND_ATMEL_SOC_SSC_PDC && SOUND && !UML && SND && SND_SOC && 
>> SND_ATMEL_SOC && ATMEL_SSC
>>
>> ---
>> 0-DAY CI Kernel Test Service, Intel Corporation
>> https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [jarkko-linux-tpmdd:next 9/10] 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem', 'r')
  2021-06-25  8:22   ` Rong Chen
@ 2021-06-25 11:58     ` Stefan Berger
  0 siblings, 0 replies; 4+ messages in thread
From: Stefan Berger @ 2021-06-25 11:58 UTC (permalink / raw)
  To: kbuild-all

[-- Attachment #1: Type: text/plain, Size: 492 bytes --]

On 6/25/21 4:22 AM, Rong Chen wrote:

>
>
> On 6/24/21 11:27 PM, Stefan Berger wrote:
>> I am at a loss with this. I tried several combinations of openssl and 
>> key being available/unavailable and they all behave as expected:
>
> Hi Stefan,
>
> I'm not sure what the difference of the test environment, the problem 
> can be reproduced in our environment:


Ah, it doesn't break the build but emits this additional error message. 
I didn't realize that.


    Stefan


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-06-25 11:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-23 22:32 [jarkko-linux-tpmdd:next 9/10] 140443843548416:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('certs/signing_key.pem', 'r') kernel test robot
2021-06-24 15:27 ` Stefan Berger
2021-06-25  8:22   ` Rong Chen
2021-06-25 11:58     ` Stefan Berger

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.