From: Herbert Xu <herbert@gondor.apana.org.au>
To: Denis Kenzior <denkenz@gmail.com>
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: Thu, 12 Oct 2023 10:33:02 +0800 [thread overview]
Message-ID: <ZSda3l7asdCr06kA@gondor.apana.org.au> (raw)
In-Reply-To: <ZSc/9nUuF/d24iO6@gondor.apana.org.au>
On Thu, Oct 12, 2023 at 08:38:14AM +0800, Herbert Xu wrote:
>
> > Narrowing down further didn't work due to:
> > /usr/bin/ld: crypto/asymmetric_keys/x509_public_key.o: in function
> > `x509_get_sig_params':
> > x509_public_key.c:(.text+0x363): undefined reference to `sm2_compute_z_digest'
> > collect2: error: ld returned 1 exit status
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.
Can you please do a clean rebuild from the first buggy commit with
the same config file and see if it still triggers the build failure?
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2023-10-12 2:33 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 [this message]
2023-10-12 3:09 ` Denis Kenzior
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=ZSda3l7asdCr06kA@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=denkenz@gmail.com \
--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