Messages in this thread Patch in this message | | | From | Neil Brown <> | Date | Thu, 10 Nov 2005 16:40:13 +1100 | Subject | Re: 2.6.14-mm1 RAID-1 in D< state |
| |
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); - 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/
| |