From: Bob Miller <rem@osdl.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.3 remove global semaphore_lock spin lock.
Date: Fri, 1 Feb 2002 14:45:07 -0800 [thread overview]
Message-ID: <20020201144507.A1419@doc.pdx.osdl.net> (raw)
In-Reply-To: <20020131150139.A1345@doc.pdx.osdl.net> <3C59D956.4F2B85DB@zip.com.au>, <3C59D956.4F2B85DB@zip.com.au> <20020201125234.A1418@doc.pdx.osdl.net> <3C5B0312.40DB82AB@zip.com.au>
In-Reply-To: <3C5B0312.40DB82AB@zip.com.au>
On Fri, Feb 01, 2002 at 01:05:22PM -0800, Andrew Morton wrote:
> Bob Miller wrote:
> >
> > Also, at your suggestion I set wait.h:USE_RW_WAIT_QUEUE_SPINLOCK on
> > a clean 2.5.3 system to test. The problem is that it OOPs on startup.
>
> OK, someone broke it; possibly the scheduler changes. Not surprising,
> really.
>
> It'd be nice to have it fixed, but I wouldn't suggest that you
> bust a gut over it. Certainly your patch shouldn't be held up by
> this. An oops trace would be useful.
>
> -
I found the problem... in kernel/sched.c around the 2.4.7 time frame
wait_for_completion() and other code was added. It uses a new
completion structure that has a wait_queue_haed_t embedded in it.
In wait_for_completion() and other places they use spin_lock_*()
calls that cause the OOPs.
In order to do some of the clean up you suggested I needed to and
some macros to wait.h. To fix wait_for_completion() and others
those same macros will be needed. I'm going to fix the wait_for_completion()
stuff first and then get back to the sema stuff.
--
Bob Miller Email: rem@osdl.org
Open Software Development Lab Phone: 503.626.2455 Ext. 17
prev parent reply other threads:[~2002-02-01 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 23:01 Bob Miller
2002-01-31 23:55 ` Andrew Morton
2002-02-01 3:41 ` Jeff Garzik
2002-02-01 15:58 ` Jens Axboe
2002-02-01 20:52 ` Bob Miller
2002-02-01 21:05 ` Andrew Morton
2002-02-01 22:45 ` Bob Miller [this message]
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=20020201144507.A1419@doc.pdx.osdl.net \
--to=rem@osdl.org \
--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
all inboxes | Powered by JetHome®