From: Andrew Morton <andrewm@uow.edu.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Vibol Hou <vhou@khmer.cc>, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: mysqld [3.2.23] hangs when key_buffer ~256MB on [2.4.2-ac28+]
Date: Wed, 04 Apr 2001 12:56:56 -0700 [thread overview]
Message-ID: <3ACB7C88.40DB16FA@uow.edu.au> (raw)
In-Reply-To: <NDBBKKONDOBLNCIOPCGHKELLFOAA.vhou@khmer.cc> from "Vibol Hou" at Apr 04, 2001 11:44:00 AM <E14ksXc-0002YN-00@the-village.bc.nu>
Alan Cox wrote:
>
> > I initially upgraded my kernel from 2.4.2-ac5 to 2.4.3 and the first thing I
> > noticed was that mysqld was stuck. Killing it left it hanging in a D state.
> > Then I tried 2.4.2-ac28 (which I am using now), and the got the same result.
>
> I'd expect that bit. 2.4.2-ac28 basically has the same new rwlock VM and
> behaviour as 2.4.3pre8. What would be really useful to know is if anyone can
> duplicate the problem non x86
>
> > Can anyone reproduce this problem?
>
> Yes
Untested patch:
--- semaphore.c.orig Wed Apr 4 12:54:30 2001
+++ semaphore.c Wed Apr 4 12:54:58 2001
@@ -363,26 +363,26 @@
*/
struct rw_semaphore *down_write_failed(struct rw_semaphore *sem)
{
struct task_struct *tsk = current;
DECLARE_WAITQUEUE(wait, tsk);
__up_write(sem); /* this takes care of granting the lock
*/
- add_wait_queue_exclusive(&sem->wait, &wait);
+ add_wait_queue_exclusive(&sem->write_bias_wait, &wait);
while (atomic_read(&sem->count) < 0) {
set_task_state(tsk, TASK_UNINTERRUPTIBLE);
if (atomic_read(&sem->count) >= 0)
break; /* we must attempt to acquire or bias
the lock */
schedule();
}
- remove_wait_queue(&sem->wait, &wait);
+ remove_wait_queue(&sem->write_bias_wait, &wait);
tsk->state = TASK_RUNNING;
return sem;
}
asm(
"
.align 4
next prev parent reply other threads:[~2001-04-04 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 18:44 mysqld [3.2.23] hangs when key_buffer ~256MB on [2.4.2-ac28+] Vibol Hou
2001-04-04 19:02 ` Alan Cox
2001-04-04 19:56 ` Andrew Morton [this message]
2001-04-05 8:17 ` Vibol Hou
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=3ACB7C88.40DB16FA@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vhou@khmer.cc \
/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