[lkml]   [2002]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [BUG] __write_lock_failed() oops
    William Lee Irwin III wrote:
    >> After running 64 simultaneous tiobench 256's a few times,
    >> I get the following oops, which I've been seeing intermittently
    >> for a number of 2.5.x releases (since 2.5.x booted on NUMA-Q):
    >> Program received signal SIGSEGV, Segmentation fault.
    >> 0xc0106693 in __write_lock_failed () at semaphore.c:176
    >> 176 semaphore.c: No such file or directory.
    >> in semaphore.c

    On Thu, Sep 05, 2002 at 01:42:52AM -0700, Andrew Morton wrote:
    > That's all the assembly hacks in the rwlock code not having proper
    > stack frames. You may have to ksymoops it.
    > At a guess: use-after-free bug against an address_space. You may
    > be able to catch it with slab poisoning.

    (gdb) p/x $eax
    $25 = 0xc0331ca0
    (gdb) p &tasklist_lock
    $27 = (rwlock_t *) 0xc0331ca0

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

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