From: Vladimir Kondratiev <vkondra@mail.ru>
To: Matt Mackall <mpm@selenic.com>
Cc: Niranjan <niranjan_cs2905@yahoo.com>, netdev@oss.sgi.com
Subject: Re: kernel bug at sched.c:564! + linux kernel 2.4.25
Date: Tue, 27 Jul 2004 21:02:39 +0300 [thread overview]
Message-ID: <200407272102.58638.vkondra@mail.ru> (raw)
In-Reply-To: <20040726210613.GR5414@waste.org>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
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?
On Tuesday 27 July 2004 00:06, Matt Mackall wrote:
> On Sat, Jul 24, 2004 at 03:33:10PM -0700, Niranjan wrote:
> > Hi,
> > I am working on Linux Kernel 2.4.25. I am trying to
> > add cryptoapi (cryptoapi-0.1.0) support to wireless
> > lan driver (linux-wlan-ng-0.2.1.pre14) of prism-based
> > cards. Cardctl version is 3.1.31.
> > When I am using "null" as a encryption cipher to check
> > the coding sequence, everything is working fine. But
> > when I change it to any other cipher for e.g.
> > "blowfish" or "rc5", it is giving kernel panic. I have
> > included Ksymoops extract from the kernel Ooops
> > reports below.
> > Can anyone please help me in what can be possible
> > error by looking at the log ?
> > I will greatly appreciate any help in this matter.
>
> The cryptoapi currently decides to sleep at various points internally
> when digesting a block which is probably what you're seeing.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-27 18:02 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 [this message]
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
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=200407272102.58638.vkondra@mail.ru \
--to=vkondra@mail.ru \
--cc=mpm@selenic.com \
--cc=netdev@oss.sgi.com \
--cc=niranjan_cs2905@yahoo.com \
/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).