From: Jean-Luc Cooke <jlcooke@certainkey.com>
To: linux-kernel@vger.kernel.org
Subject: CryptoAPI: schedual while atomic
Date: Mon, 30 Aug 2004 09:24:53 -0400 [thread overview]
Message-ID: <20040830132453.GG11307@certainkey.com> (raw)
While I was playing with using the CryptoAPI in /dev/random for my own
purposes, I noticed that I was getting quite a few "schedual while atomic!"
console messages.
Talking with Michal Ludvig, I seem to think that a "!is_atomic()" check
inside crypto_yield() or passing a flag during crypto_alloc_tfm() would make
a lot of sense.
This may be more directed at James Morris, but here it goes:
Can we have some logic to either check for or turn off crypto_yield()'s in
crypto/internal.h's crypto_yield() ?
Cheers,
JLC
next reply other threads:[~2004-08-30 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 13:24 Jean-Luc Cooke [this message]
2004-08-30 14:42 ` CryptoAPI: schedual while atomic James Morris
2004-08-30 13:53 ` Jean-Luc Cooke
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=20040830132453.GG11307@certainkey.com \
--to=jlcooke@certainkey.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.