From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: linux-crypto <linux-crypto@vger.kernel.org>
Subject: Re: cipher implementations allowed to sleep?
Date: Thu, 31 Mar 2016 20:58:25 +0800 [thread overview]
Message-ID: <20160331125825.GA30134@gondor.apana.org.au> (raw)
In-Reply-To: <5387862.2PP9F0yuod@tauon.atsec.com>
On Thu, Mar 31, 2016 at 01:47:50PM +0200, Stephan Mueller wrote:
>
> Considering the implementation in ansi_cprng.c, is it allowed to use
> spin_lock_bh with the sync operations assuming that a cipher implementation
> may sleep?
As I said, it's only allowed to sleep if you set the MAY_SLEEP
flag.
Cheers,
--
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
next prev parent reply other threads:[~2016-03-31 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 9:18 cipher implementations allowed to sleep? Stephan Mueller
2016-03-31 9:21 ` Herbert Xu
2016-03-31 9:39 ` Stephan Mueller
2016-03-31 11:47 ` Stephan Mueller
2016-03-31 12:58 ` Herbert Xu [this message]
2016-03-31 13:02 ` Stephan Mueller
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=20160331125825.GA30134@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=smueller@chronox.de \
/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