From: Jack Wang <jinpu.wang@profitbricks.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, Jack Wang <xjtuwjp@gmail.com>,
Sebastian Riemer <sebastian.riemer@profitbricks.com>
Subject: Re: [BUG] md hang at schedule in md_write_start
Date: Tue, 13 Aug 2013 09:42:53 +0200 [thread overview]
Message-ID: <5209E37D.6050107@profitbricks.com> (raw)
In-Reply-To: <20130813143115.55dd27d1@notabene.brown>
On 08/13/2013 06:31 AM, NeilBrown wrote:
> On Mon, 12 Aug 2013 18:33:49 +0200 Jack Wang <jinpu.wang@profitbricks.com>
> wrote:
>
>> Hi Neil,
>>
>>
>> We've found md hang in our test, it's easy to reproduce with script
>> attached.
>>
>> We've tried 3.4 stable kernel and latest mainline, it still exists.
>>
>> Looks like flush bdi_writeback_workfn race with md_stop, no idea how to
>> fix it, could you kindly give us suggestions?
>>
>> Best regards,
>> Jack
>
> Thanks for the report. I can see how that deadlock could happen.
>
> Can you please try this patch and confirm that it fixes it.
> I'm not really happy with this approach but nothing better occurs to me yet.
>
> NeilBrown
>
Hi Neil,
Thanks for quick fix, I tested on 3.4 stable and mainline, it works now.
Could you give more description about the bug and fix.
Regards,
Jack
next prev parent reply other threads:[~2013-08-13 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 16:33 [BUG] md hang at schedule in md_write_start Jack Wang
2013-08-13 4:31 ` NeilBrown
2013-08-13 7:42 ` Jack Wang [this message]
2013-08-14 0:44 ` NeilBrown
2013-08-14 8:09 ` Jack Wang
2013-09-10 11:09 ` Jack Wang
2013-09-10 23:54 ` NeilBrown
2013-09-11 7:40 ` Jack Wang
2013-09-11 22:59 ` NeilBrown
2013-09-12 7:55 ` Jack Wang
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=5209E37D.6050107@profitbricks.com \
--to=jinpu.wang@profitbricks.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sebastian.riemer@profitbricks.com \
--cc=xjtuwjp@gmail.com \
/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.