From: James Morris <jmorris@intercode.com.au>
To: Jochen Hein <jochen@jochen.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, <yoshfuji@linux-ipv6.org>
Subject: Re: [2.5.64, IPv6] sleeping function called from illegal context
Date: Wed, 5 Mar 2003 20:22:58 +1100 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303052015370.21996-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <87k7fefc70.fsf@jupiter.jochen.org>
On Wed, 5 Mar 2003, Jochen Hein wrote:
>
> The console output is:
>
> Debug: sleeping function called from illegal context at
> include/linux/rwsem.h:43
> Call Trace:
> [<c0116478>] __might_sleep+0x54/0x5c
> [<c01cab41>] crypto_alg_lookup+0x21/0xc8
> [<c01cb971>] crypto_alg_mod_lookup+0xd/0x2c
> [<c01cacfd>] crypto_alloc_tfm+0x11/0xc0
> [<c02c1240>] __ipv6_regen_rndid+0xa0/0x1f4
> [<c01149fd>] wake_up_process+0xd/0x14
> [<c02c13c2>] ipv6_regen_rndid+0x2e/0xc4
> [<c011eeb9>] run_timer_softirq+0xf1/0x144
> [<c02c1394>] ipv6_regen_rndid+0x0/0xc4
> [<c011b761>] do_softirq+0x51/0xb0
> [<c010a230>] do_IRQ+0x114/0x130
> [<c0106f54>] default_idle+0x0/0x34
> [<c0106f54>] default_idle+0x0/0x34
> [<c0108ea0>] common_interrupt+0x18/0x20
> [<c0106f54>] default_idle+0x0/0x34
> [<c0106f54>] default_idle+0x0/0x34
> [<c0106f7a>] default_idle+0x26/0x34
> [<c0107009>] cpu_idle+0x35/0x44
> [<c0105000>] rest_init+0x0/0x5c
> [<c0105055>] rest_init+0x55/0x5c
>
> __ipv6_regen_rndid(): too short regeneration interval; timer diabled
> for eth0.
Crypto transforms cannot be allocated in interrupt context or while
holding a spinlock. It seems that at least the latter is happening in
ipv6_regen_rndid().
The transform needs to be allocated prior to use in this case.
- James
--
James Morris
<jmorris@intercode.com.au>
prev parent reply other threads:[~2003-03-05 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 8:29 Jochen Hein
2003-03-05 9:22 ` James Morris [this message]
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=Pine.LNX.4.44.0303052015370.21996-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=jochen@jochen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®