Linux cryptographic layer development
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: matorola@gmail.com
Cc: linux-crypto@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [crypto / sparc64] cryptomgr_test OOPS
Date: Tue, 03 May 2016 12:33:01 -0400 (EDT)	[thread overview]
Message-ID: <20160503.123301.298039059390449291.davem@davemloft.net> (raw)
In-Reply-To: <CADxRZqyMwme53etMrnx3xkpGsR6-W88RHLA3nh0GCGAzcz5=Fw@mail.gmail.com>

From: Anatoly Pugachev <matorola@gmail.com>
Date: Tue, 3 May 2016 16:54:18 +0300

> I have git kernel OOPS (4.6.0-rc6) on sparc64. This OOPS does not
> happen, if I set the following kernel option:
> 
> CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
> 
> Can someone please look at https://bugzilla.kernel.org/show_bug.cgi?id=117551 ?

The lib/mpi/ code hasn't been touched in a long time, so I can only see that it might
be the crypto/rsa.c changes that happened this release.

Can you possibly bisect this or at least tell us that 4.5 doesn't have this problem?

  reply	other threads:[~2016-05-03 16:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 13:54 [crypto / sparc64] cryptomgr_test OOPS Anatoly Pugachev
2016-05-03 16:33 ` David Miller [this message]
2016-05-04  4:07   ` Herbert Xu
2016-05-04 14:49     ` Anatoly Pugachev
2016-05-05  8:42       ` Herbert Xu
2016-05-05  9:40         ` Anatoly Pugachev
2016-05-05  9:50           ` Herbert Xu
2016-05-05 16:17             ` Tadeusz Struk
2016-05-05 15:00           ` Tadeusz Struk
2016-05-05 15:31             ` Anatoly Pugachev
2016-05-05 15:52               ` John Paul Adrian Glaubitz
2016-05-05 16:09               ` Tadeusz Struk
2016-05-05 15:12         ` Anatoly Pugachev
2016-05-05 15:17           ` John Paul Adrian Glaubitz
2016-05-06 19:52         ` David Miller
2016-05-04 19:10   ` Anatoly Pugachev
2016-05-04 20:02     ` Tadeusz Struk
2016-05-04 20:51     ` David Miller

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=20160503.123301.298039059390449291.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=matorola@gmail.com \
    --cc=sparclinux@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