On Tuesday 27 July 2004 21:39, James Morris wrote:
> On Tue, 27 Jul 2004, Vladimir Kondratiev wrote:
> > We also saw the same (crypto modules goes to sleep).
> > Due to this, we decided to not use cryptoapi for our wireless driver, but
> > compile the same crypto functions into the driver. I know this is code
> > duplication, but Tx and Rx paths work in BH context (I reschedule it on
> > IRQ Rx to use cheaper time).
> >
> > Do cryptoapi maintainers aware of this issue?
>
> The crypto functions should be safe to use in softirq context.
It should be, but:
<crypto/api.c:121>
struct crypto_tfm *crypto_alloc_tfm(const char *name, u32 flags)
{
struct crypto_tfm *tfm = NULL;
struct crypto_alg *alg;
alg = crypto_alg_mod_lookup(name);
if (alg == NULL)
goto out;
tfm = kmalloc(sizeof(*tfm) + alg->cra_ctxsize, GFP_KERNEL);
Note kmalloc(GFP_KERNEL)
>
>
> - James
pgpXNESXTkW5b.pgp
Description: PGP signature
|