All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: "Jethro Beekman - E.T.S.V. Scintilla"
	<jethrob@scintilla.utwente.nl>,
	linux-crypto@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [Bug 37862] padlock related kernel NULL pointer dereference
Date: Thu, 28 Jul 2011 17:34:08 +0800	[thread overview]
Message-ID: <20110728093408.GA5757@gondor.apana.org.au> (raw)
In-Reply-To: <201107280920.p6S9KDhw003188@demeter1.kernel.org>

On Thu, Jul 28, 2011 at 09:20:13AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=37862
> 
> 
> 
> 
> 
> --- Comment #10 from Jethro Beekman <kernel@jbeekman.nl>  2011-07-28 09:20:13 ---
> That is interesting, on 
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.26.y.git;a=history;f=drivers/crypto
> that particular patch is included but on
> https://github.com/mirrors/linux-2.6/commits/v2.6.26/drivers/crypto
> it isn't.
> 
> Anyway, my distro's kernel source package has the patch applied.

OK, it does seem that it was applied.  Suresh, any ideas what
might be wrong here? The crash looks eerily like the one that
was fixed by your patch.

> I will try to use the latest kernel, but in the very near future I won't be
> able to test on that system. In that case, I will try to get a colleague
> working on this.

Please do.

Thanks,
-- 
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

           reply	other threads:[~2011-07-28  9:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201107280920.p6S9KDhw003188@demeter1.kernel.org>]

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=20110728093408.GA5757@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=jethrob@scintilla.utwente.nl \
    --cc=linux-crypto@vger.kernel.org \
    --cc=suresh.b.siddha@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.