public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [BUG] ut lib lib_rsa_verify_valid crashes on qemu_arm if RSA_VERIFY_WITH_PKEY=y
Date: Tue, 9 Jun 2020 10:42:14 +0900	[thread overview]
Message-ID: <20200609014214.GA19948@laputa> (raw)
In-Reply-To: <d481c877-9a4c-9cea-2abc-5e226c3a31e5@gmx.de>

Heinrich,

On Mon, Jun 08, 2020 at 11:08:53PM +0200, Heinrich Schuchardt wrote:
> Hello Takahiro,
> 
> when trying to execute command
> 
> ut lib lib_rsa_verify_valid
> 
> on qemu_arm_defconfig with CONFIG_UNIT_TEST=y and
> CONFIG_RSA_VERIFY_WITH_PKEY=y it crashes in
> 
> free((void *)prop->modulus) called from
> rsa_free_key_prop() called from
> rsa_verify_key() called from
> rsa_verify_with_pkey().
> 
> Without CONFIG_RSA_VERIFY_WITH_PKEY=y the problem does not occur.
> On qemu_arm64_defconfig the problem does not occur.

I can't reproduce your problem on v2020.07-rc4 exactly with
qemu_arm64_defconfig + PKEY=y:

U-Boot 2020.07-rc4-dirty (Jun 09 2020 - 10:33:30 +0900)

...

=> ut lib
Running 11 lib tests
Test: lib_asn1_pkcs7
Test: lib_asn1_pkey
Test: lib_asn1_x509
Test: lib_memcpy
Test: lib_memmove
Test: lib_memset
Test: lib_rsa_verify_invalid
Test: lib_rsa_verify_valid
Test: lib_test_bin2hex
Test: lib_test_hex2bin
Test: lib_test_hex_to_bin
Failures: 0


-Takahiro Akashi

> Could you, please, have a look.
> 
> Best regards
> 
> Heinrich

  reply	other threads:[~2020-06-09  1:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 21:08 [BUG] ut lib lib_rsa_verify_valid crashes on qemu_arm if RSA_VERIFY_WITH_PKEY=y Heinrich Schuchardt
2020-06-09  1:42 ` AKASHI Takahiro [this message]
2020-06-09  3:54   ` Heinrich Schuchardt
2020-06-09  9:22     ` AKASHI Takahiro
2020-06-09 10:11       ` Heiko Stübner
2020-06-09 10:22         ` Heinrich Schuchardt
2020-06-09 10:45           ` Heiko Stübner

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=20200609014214.GA19948@laputa \
    --to=takahiro.akashi@linaro.org \
    --cc=u-boot@lists.denx.de \
    /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