public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jim Davis <jim.epost@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Herbert Xu <herbert@gondor.hengli.com.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org
Subject: Re: randconfig build error with next-20131002, in crypto
Date: Thu, 3 Oct 2013 01:56:15 +0200	[thread overview]
Message-ID: <20131002235615.GA7419@pd.tnic> (raw)
In-Reply-To: <CA+r1ZhgsXTZ_x-jzS2OpjryhCExrG0B6nB_Ph4gb9_BJL4zeCA@mail.gmail.com>

On Wed, Oct 02, 2013 at 03:19:51PM -0700, Jim Davis wrote:
> Building with the attached random configuration file,
> 
>   LD      init/built-in.o
> crypto/built-in.o: In function `RSA_verify_signature':
> rsa.c:(.text+0x2dc5e): undefined reference to `mpi_get_nbits'
> rsa.c:(.text+0x2dc68): undefined reference to `mpi_get_nbits'
> rsa.c:(.text+0x2dc89): undefined reference to `mpi_free'
> rsa.c:(.text+0x2dca4): undefined reference to `mpi_cmp_ui'
> rsa.c:(.text+0x2dcb7): undefined reference to `mpi_cmp'
> rsa.c:(.text+0x2dcc6): undefined reference to `mpi_alloc'
> rsa.c:(.text+0x2dce7): undefined reference to `mpi_powm'
> rsa.c:(.text+0x2dcff): undefined reference to `mpi_get_nbits'
> rsa.c:(.text+0x2dd1c): undefined reference to `mpi_get_buffer'
> rsa.c:(.text+0x2de07): undefined reference to `mpi_free'
> make: *** [vmlinux] Error 1

Looks like someone has forgotten this completely unused MPILIB_EXTRA
thing in there.

Does this totally untested but obvious patch help?

---
From: Borislav Petkov <bp@suse.de>
Date: Thu, 3 Oct 2013 01:51:15 +0200
Subject: [PATCH] crypto: Correct RSA MPI dependency

9e235dcaf4f6 ("Revert "crypto: GnuPG based MPI lib - additional sources
(part 4)") removed the MPI lib extra stuff but left RSA selecting it
while it should select CONFIG_MPILIB instead. Fix it.

Reported-by: Jim Davis <jim.epost@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: David Howells <dhowells@redhat.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
---
 crypto/asymmetric_keys/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crypto/asymmetric_keys/Kconfig b/crypto/asymmetric_keys/Kconfig
index 6d2c2ea12559..755f6174585a 100644
--- a/crypto/asymmetric_keys/Kconfig
+++ b/crypto/asymmetric_keys/Kconfig
@@ -21,7 +21,7 @@ config ASYMMETRIC_PUBLIC_KEY_SUBTYPE
 config PUBLIC_KEY_ALGO_RSA
 	tristate "RSA public-key algorithm"
 	depends on ASYMMETRIC_PUBLIC_KEY_SUBTYPE
-	select MPILIB_EXTRA
+	select MPILIB
 	help
 	  This option enables support for the RSA algorithm (PKCS#1, RFC3447).
 
-- 
1.8.4

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-10-02 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 22:19 randconfig build error with next-20131002, in crypto Jim Davis
2013-10-02 23:56 ` Borislav Petkov [this message]
2013-10-03  2:54   ` Jim Davis
2013-10-03  8:25     ` [PATCH] crypto: Correct RSA MPI dependency Borislav Petkov

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=20131002235615.GA7419@pd.tnic \
    --to=bp@alien8.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.hengli.com.au \
    --cc=jim.epost@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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