From: Keith Owens <kaos@ocs.com.au>
To: Neil Brown <neilb@suse.de>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc4 md lock held at task exit
Date: Tue, 23 May 2006 15:56:47 +1000 [thread overview]
Message-ID: <9193.1148363807@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Fri, 12 May 2006 17:11:11 +1000." <17508.13583.730399.209905@cse.unsw.edu.au>
Neil Brown (on Fri, 12 May 2006 17:11:11 +1000) wrote:
>On Friday May 12, kaos@ocs.com.au wrote:
>> Doing poweroff on 2.6.17-rc4 i386, SMP
>>
>> BUG halt/4781, lock held at task exit time!
>> [f7001b34] {mddev_find}
>> .. held by: halt: 4781 [f7cd4030, 118]
>> ... acquired at: md_notify_reboot+0x3a/0xa9 [md_mod}
>>
>
>I suspect this will fix it.
>Is it repeatable? Can you test?
>
>Thanks,
>NeilBrown
>
>
>Signed-off-by: Neil Brown <neilb@suse.de>
>
>### Diffstat output
> ./drivers/md/md.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>diff ./drivers/md/md.c~current~ ./drivers/md/md.c
>--- ./drivers/md/md.c~current~ 2006-05-12 16:00:03.000000000 +1000
>+++ ./drivers/md/md.c 2006-05-12 17:10:16.000000000 +1000
>@@ -5171,8 +5171,10 @@ static int md_notify_reboot(struct notif
> printk(KERN_INFO "md: stopping all md devices.\n");
>
> ITERATE_MDDEV(mddev,tmp)
>- if (mddev_trylock(mddev))
>+ if (mddev_trylock(mddev)) {
> do_md_stop (mddev, 1);
>+ mddev_unlock(mddev);
>+ }
> /*
> * certain more exotic SCSI devices are known to be
> * volatile wrt too early system reboots. While the
Finally got some time to test this. The problem was reproducable and
the patch fixed it.
Acked-by: Keith Owens <kaos@ocs.com.au>
next prev parent reply other threads:[~2006-05-23 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 6:43 Keith Owens
2006-05-12 7:11 ` Neil Brown
2006-05-23 5:56 ` Keith Owens [this message]
2006-05-23 6:05 ` Neil Brown
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=9193.1148363807@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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®