From: Jean-Luc Cooke <jlcooke@certainkey.com>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CryptoAPI: schedual while atomic
Date: Mon, 30 Aug 2004 09:53:51 -0400 [thread overview]
Message-ID: <20040830135351.GJ11307@certainkey.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0408301040200.21963-100000@thoron.boston.redhat.com>
On Mon, Aug 30, 2004 at 10:42:11AM -0400, James Morris wrote:
> Where is the code which caused this? The transforms are safe to use (but
> not allocate) in process and softirq contexts.
In add_entropy_words of random.c my experimental code is calling
crypto_digest_update(). In update() it calles crypto_yield.
add_entropy_words() is being call ed directly from a keyboard_interrupt. I
was hoping to tidy up the code a bit by not using batch_entropy_stores... but
I guess that's unavoidable then?
Last question:
Would spin_lock_irqsave() spin_unlock_irqrestore() still needed to surround
crypto_digest_update() calls if they're going to be scattered/gathered
later?
Thanks for your time.
JLC
next prev parent reply other threads:[~2004-08-30 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 13:24 CryptoAPI: schedual while atomic Jean-Luc Cooke
2004-08-30 14:42 ` James Morris
2004-08-30 13:53 ` Jean-Luc Cooke [this message]
2004-08-30 15:06 ` James Morris
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=20040830135351.GJ11307@certainkey.com \
--to=jlcooke@certainkey.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@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 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.