From: Andrew Morton <akpm@digeo.com>
To: Steven Cole <scole@lanl.gov>
Cc: lkml <linux-kernel@vger.kernel.org>, netfilter-devel@lists.netfilter.org
Subject: Re: Sleeping function called from illegal context at slab.c:1378
Date: Mon, 23 Sep 2002 11:30:10 -0700 [thread overview]
Message-ID: <3D8F5DB2.A3E36E16@digeo.com> (raw)
In-Reply-To: 1032804558.28404.13.camel@spc9.esa.lanl.gov
That's a bug in ip_fw_ctl(). It's calling convert_ipfw()
inside FWC_WRITE_LOCK_IRQ(&ip_fw_lock, flags);
But convert_ipfw() does kmalloc(GFP_KERNEL).
Steven Cole wrote:
>
> Hi Andrew,
>
> Are these traced warnings of any use to you?
>
> If so, here is one. This one was from
>
> "Sleeping function called from illegal context at slab.c:1378"
>
> on bootup of 2.5.38-mm2:
>
> Trace; c0119986 <__might_sleep+56/5d>
> Trace; c0135166 <kmalloc+66/1f0>
> Trace; c0271e03 <convert_ipfw+63/130>
> Trace; c02721c0 <ip_fw_ctl+2f0/4d0>
> Trace; c026a023 <sock_fn+63/80>
> Trace; c012ff2e <find_get_page+2e/60>
> Trace; c0130db5 <filemap_nopage+115/310>
> Trace; c012d8ef <do_no_page+2ef/390>
> Trace; c012b5ba <pte_alloc_map+ea/150>
> Trace; c023471a <nf_sockopt+fa/150>
> Trace; c0234790 <nf_setsockopt+20/30>
> Trace; c0242fda <ip_setsockopt+74a/910>
> Trace; c02255de <sock_map_fd+be/120>
> Trace; c022562a <sock_map_fd+10a/120>
> Trace; c0263995 <inet_setsockopt+25/30>
> Trace; c02269d6 <sys_setsockopt+56/70>
> Trace; c0227026 <sys_socketcall+1a6/200>
> Trace; c0114ea0 <do_page_fault+0/436>
> Trace; c01099b1 <error_code+2d/38>
> Trace; c0108f6f <syscall_call+7/b>
>
> Steven
next parent reply other threads:[~2002-09-23 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1032804558.28404.13.camel@spc9.esa.lanl.gov>
2002-09-23 18:30 ` Andrew Morton [this message]
2002-09-23 20:00 ` Sleeping function called from illegal context at slab.c:1378 Steven Cole
2002-09-23 20:21 ` Andrew Morton
2002-09-23 20:43 ` Steven Cole
2002-09-23 20:49 ` Nuno Monteiro
2002-09-23 21:30 ` Andrew Morton
2002-09-24 13:34 ` James Morris
2002-09-24 14:53 ` [PATCH] " 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=3D8F5DB2.A3E36E16@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=scole@lanl.gov \
/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.