Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	davem@davemloft.net,
	Eric Sesterhenn <eric.sesterhenn@lsexperts.de>
Subject: Re: [PATCH 2/2] crypto/ansi prng: alloc cipher just in in init()
Date: Mon, 29 Jun 2009 23:48:21 +0200	[thread overview]
Message-ID: <20090629214821.GC29616@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <20090629214508.GB29616@Chamillionaire.breakpoint.cc>

* Sebastian Andrzej Siewior | 2009-06-29 23:45:08 [+0200]:

>From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
>
>As reported by Eric Sesterhenn the re-allocation of the cipher in reset leads

Neil, the patches are untested. Could you please verify them?

Sebastian

  reply	other threads:[~2009-06-29 21:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 13:17 Bug when modprobing tcrypt Eric Sesterhenn
2009-06-29 14:07 ` Sebastian Andrzej Siewior
2009-06-29 15:20   ` Neil Horman
2009-06-29 21:44     ` [PATCH 1/2] crypto/ansi prng: use just a BH lock Sebastian Andrzej Siewior
2009-06-30 14:14       ` Neil Horman
2009-06-29 21:45     ` [PATCH 2/2] crypto/ansi prng: alloc cipher just in in init() Sebastian Andrzej Siewior
2009-06-29 21:48       ` Sebastian Andrzej Siewior [this message]
2009-06-29 21:54         ` Neil Horman
2009-06-30 14:51       ` Neil Horman
2009-06-30 19:55         ` [PATCH v2] " Sebastian Andrzej Siewior
2009-07-01  0:06           ` Neil Horman
     [not found]             ` <20090701072517.GA9583@Chamillionaire.breakpoint.cc>
2009-07-01 10:36               ` Neil Horman
2009-07-03  4:11                 ` Herbert Xu

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=20090629214821.GC29616@Chamillionaire.breakpoint.cc \
    --to=sebastian@breakpoint.cc \
    --cc=davem@davemloft.net \
    --cc=eric.sesterhenn@lsexperts.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=nhorman@tuxdriver.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