From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] __write_lock_failed() oops
Date: Thu, 5 Sep 2002 01:32:40 -0700 [thread overview]
Message-ID: <20020905083240.GC888@holomorphy.com> (raw)
In-Reply-To: <3D77190C.F4562547@zip.com.au>
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
next prev parent reply other threads:[~2002-09-05 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 8:03 [BUG] __write_lock_failed() oops William Lee Irwin III
2002-09-05 8:42 ` Andrew Morton
2002-09-05 8:32 ` William Lee Irwin III [this message]
2002-09-05 8:45 ` William Lee Irwin III
2002-09-05 8:59 ` William Lee Irwin III
2002-09-05 9:08 ` William Lee Irwin III
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=20020905083240.GC888@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--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