public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	James Prestwood <prestwoj@gmail.com>
Subject: Re: Linux 6.5 broke iwd
Date: Wed, 11 Oct 2023 22:09:02 -0500	[thread overview]
Message-ID: <be96d2e7-592e-467e-9ad2-3f69a69cf844@gmail.com> (raw)
In-Reply-To: <ZSda3l7asdCr06kA@gondor.apana.org.au>

Hi Herbert,

> 
> I wonder if this is a bug in the bisection process.  The reference
> to sm2_compute_z_digest is protected by an IS_REACHABLE test on
> SM2 which is presumably disabled in your configuration.

So I just tried this again, here are the exact steps.  I believe the sha1 below 
was next in the bisect process.

[denkenz@archdev linux]$ git checkout 63ba4d67594ad05b2c899b5a3a8cc7581052dd13
HEAD is now at 63ba4d67594a KEYS: asymmetric: Use new crypto interface without 
scatterlists
[denkenz@archdev linux]$ make ARCH=um x86_64_defconfig
#
# configuration written to .config
#
[denkenz@archdev linux]$ ARCH=um sh ~/iwd-master/tools/test_runner_kernel_config
[denkenz@archdev linux]$ make ARCH=um olddefconfig
#
# configuration written to .config
#
[denkenz@archdev linux]$ make clean
   CLEAN   crypto/asymmetric_keys
   CLEAN   drivers/base/firmware_loader/builtin
   CLEAN   init
   CLEAN   kernel
   CLEAN   lib
   CLEAN   .
   CLEAN   modules.builtin modules.builtin.modinfo .vmlinux.export.c
[denkenz@archdev linux]$ make ARCH=um -j16

...

/usr/bin/ld: crypto/asymmetric_keys/x509_public_key.o: in function 
`x509_get_sig_params':
/home/denkenz/devel/linux/crypto/asymmetric_keys/x509_public_key.c:70:(.text+0x390): 
undefined reference to `sm2_compute_z_digest'

Regards,
-Denis

  reply	other threads:[~2023-10-12  3:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 17:11 Linux 6.5 broke iwd Denis Kenzior
2023-10-12  0:38 ` Herbert Xu
2023-10-12  2:18   ` Denis Kenzior
2023-10-12  2:26     ` Herbert Xu
2023-10-12  2:33   ` Herbert Xu
2023-10-12  3:09     ` Denis Kenzior [this message]
2023-10-12  3:28       ` Herbert Xu
2023-10-12 14:19         ` Denis Kenzior
2023-10-12 14:28           ` Herbert Xu
2023-10-12 15:08             ` Denis Kenzior
2023-10-16  8:35               ` [PATCH] KEYS: asymmetric: Fix sign/verify on pkcs1pad without a hash Herbert Xu
2023-10-16 19:37                 ` Denis Kenzior

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=be96d2e7-592e-467e-9ad2-3f69a69cf844@gmail.com \
    --to=denkenz@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=prestwoj@gmail.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