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
Cheers,
Bill
-
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/
This archive was generated by hypermail 2b29 : Sat Sep 07 2002 - 22:00:24 EST