From: Andrew Morton <akpm@digeo.com>
To: Burton Windle <bwindle@fint.org>,
Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.46-bk3: BUG in skbuff.c:178
Date: Fri, 08 Nov 2002 12:01:27 -0800 [thread overview]
Message-ID: <3DCC1817.3DBBAFED@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.43.0211081440130.317-100000@morpheus
Burton Windle wrote:
>
> Single-CPU system, running 2.5.46-bk3. Whiling compiling bk4, and running
> a script that was pinging every host on my subnet (I was running arp -a
> to see what was in the arp table at the time), I hit this BUG.
>
> Debug: sleeping function called from illegal context at mm/slab.c:1305
> Call Trace:
> [<c011247c>] __might_sleep+0x54/0x58
> [<c012a3e2>] kmem_flagcheck+0x1e/0x50
> [<c012ab6a>] kmem_cache_alloc+0x12/0xc8
> [<c0226e0c>] sock_alloc_inode+0x10/0x68
> [<c014cb65>] alloc_inode+0x15/0x180
> [<c014d397>] new_inode+0xb/0x78
> [<c0227093>] sock_alloc+0xf/0x68
> [<c0227d65>] sock_create+0x8d/0xe4
> [<c0227dd9>] sys_socket+0x1d/0x58
> [<c0228a13>] sys_socketcall+0x5f/0x1f4
> [<c0108903>] syscall_call+0x7/0xb
>
> bad: scheduling while atomic!
Something somewhere has caused a preempt_count imbalance. What
you're seeing here are the downstream effects of an earlier bug.
I'd be suspecting the seq_file conversion in arp.c. The read_lock_bh()
stuff in there looks, umm, unclear ;)
(Could we pleeeeze nuke the __inline__'s in there too?)
next prev parent reply other threads:[~2002-11-08 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 19:42 2.5.46-bk3: BUG in skbuff.c:178 Burton Windle
2002-11-08 20:01 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 19:33 Petr Vandrovec
2002-11-08 22:02 ` Petr Vandrovec
2002-11-10 4:18 ` Arnaldo Carvalho de Melo
2002-11-11 2:26 ` Petr Vandrovec
2002-11-11 2:42 ` Arnaldo Carvalho de Melo
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=3DCC1817.3DBBAFED@digeo.com \
--to=akpm@digeo.com \
--cc=acme@conectiva.com.br \
--cc=bwindle@fint.org \
--cc=linux-kernel@vger.kernel.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