From: "J.A. Magallon" <jamagallon@able.es>
To: Neil Brown <neilb@suse.de>
Cc: Chris Boot <bootc@bootc.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-mm1 RAID-1 in D< state
Date: Thu, 10 Nov 2005 10:37:26 +0100 [thread overview]
Message-ID: <20051110103726.35e54d65@werewolf.auna.net> (raw)
In-Reply-To: <17266.56637.123797.468396@cse.unsw.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
On Thu, 10 Nov 2005 16:40:13 +1100, Neil Brown <neilb@suse.de> wrote:
>
> Thanks for the trace. I see what is happening.
> I changed
> wait_event_timeout_interruptible
> in md.c(md_thread) to
> wait_event_timeout
>
> as the thread no longer needs to be able to respond the signals.
> However that has the side-effect of putting the process in the 'D'
> state and adding to the 'uptime'.
>
> I guess I'll put that back...
>
> NeilBrown
>
>
> Signed-off-by: Neil Brown <neilb@suse.de>
>
> ### Diffstat output
> ./drivers/md/md.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff ./drivers/md/md.c~current~ ./drivers/md/md.c
> --- ./drivers/md/md.c~current~ 2005-11-10 16:39:04.000000000 +1100
> +++ ./drivers/md/md.c 2005-11-10 16:39:28.000000000 +1100
> @@ -3439,10 +3439,11 @@ static int md_thread(void * arg)
> allow_signal(SIGKILL);
> while (!kthread_should_stop()) {
>
> - wait_event_timeout(thread->wqueue,
> - test_bit(THREAD_WAKEUP, &thread->flags)
> - || kthread_should_stop(),
> - thread->timeout);
> + wait_event_timeout_interruptible
> + (thread->wqueue,
> + test_bit(THREAD_WAKEUP, &thread->flags)
> + || kthread_should_stop(),
> + thread->timeout);
> try_to_freeze();
>
> clear_bit(THREAD_WAKEUP, &thread->flags);
s/wait_event_timeout_interruptible/wait_event_interruptible_timeout/
;)
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.1 (Cooker) for i586
Linux 2.6.14-jam1 (gcc 4.0.2 (4.0.2-1mdk for Mandriva Linux release 2006.1))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-11-10 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 13:32 2.6.14-mm1 RAID-1 in D< state Chris Boot
2005-11-09 21:12 ` J.A. Magallon
2005-11-09 22:23 ` Neil Brown
2005-11-09 23:15 ` Chris Boot
2005-11-10 5:40 ` Neil Brown
2005-11-10 9:37 ` Chris Boot
2005-11-10 9:39 ` Neil Brown
2005-11-10 9:51 ` Chris Boot
2005-11-10 9:37 ` J.A. Magallon [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=20051110103726.35e54d65@werewolf.auna.net \
--to=jamagallon@able.es \
--cc=bootc@bootc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.