lkml.org 
[lkml]   [2002]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.5.46-bk3: BUG in skbuff.c:178
    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?)
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:30    [W:0.027 / U:35.300 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site