From: Niranjan <niranjan_cs2905@yahoo.com>
To: James Morris <jmorris@redhat.com>, Vladimir Kondratiev <vkondra@mail.ru>
Cc: Matt Mackall <mpm@selenic.com>,
Niranjan <niranjan_cs2905@yahoo.com>,
netdev@oss.sgi.com
Subject: Re: kernel bug at sched.c:564! + linux kernel 2.4.25
Date: Wed, 28 Jul 2004 08:55:57 -0700 (PDT) [thread overview]
Message-ID: <20040728155557.38198.qmail@web53006.mail.yahoo.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0407271456220.7908-100000@dhcp83-76.boston.redhat.com>
Hi,
I got the code working by including the encrypt() and
decrypt() function inside the WLAN driver.
Is there any better way to get the CrytoAPI code
working from the driver or some other CryptoAPI
implementation ?
Warm Regards,
-Niranjan
--- James Morris <jmorris@redhat.com> wrote:
> On Tue, 27 Jul 2004, Vladimir Kondratiev wrote:
>
> > > 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);
> >
>
> By crypto functions I meant encrypt() decrypt() etc,
> not the allocation.
>
>
> - James
> --
> James Morris
> <jmorris@redhat.com>
>
>
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-07-28 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 22:33 kernel bug at sched.c:564! + linux kernel 2.4.25 Niranjan
2004-07-26 21:06 ` Matt Mackall
2004-07-27 18:02 ` Vladimir Kondratiev
2004-07-27 18:39 ` James Morris
2004-07-27 18:50 ` Vladimir Kondratiev
2004-07-27 18:57 ` James Morris
2004-07-28 15:55 ` Niranjan [this message]
2004-07-28 16:10 ` James Morris
2004-07-28 16:30 ` Niranjan
2004-07-27 22:23 ` Niranjan
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=20040728155557.38198.qmail@web53006.mail.yahoo.com \
--to=niranjan_cs2905@yahoo.com \
--cc=jmorris@redhat.com \
--cc=mpm@selenic.com \
--cc=netdev@oss.sgi.com \
--cc=vkondra@mail.ru \
/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;
as well as URLs for NNTP newsgroup(s).