From: Jack Wang <xjtuwjp@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: Jack Wang <jinpu.wang@profitbricks.com>,
linux-raid@vger.kernel.org,
Sebastian Riemer <sebastian.riemer@profitbricks.com>,
stable@vger.kernel.org
Subject: Re: [BUG] md hang at schedule in md_write_start
Date: Wed, 11 Sep 2013 09:40:08 +0200 [thread overview]
Message-ID: <52301E58.7010000@gmail.com> (raw)
In-Reply-To: <20130911095459.086d532d@notabene.brown>
On 09/11/2013 01:54 AM, NeilBrown wrote:
> On Tue, 10 Sep 2013 13:09:05 +0200 Jack Wang <jinpu.wang@profitbricks.com>
> wrote:
>
>> snip
>>
>> Hi Neil,
>>
>> I notice you send out pull request for md update, which include fix for
>> this bug.
>>
>> I think we'd better include the fix to stable tree at least from 3.4
>> above, what do you think?
>
> I don't think it is a situation that is at all like to occur in normal usage,
> so it doesn't seem justified for -stable.
>
> Do you disagree? Did you ever experience the deadlock in normal usage or
> only in artificial situations?
Yes, we do see this BUG in our production environment, so I think it's
good to include it in stable tree.
>
>>
>> md: avoid deadlock when dirty buffers during md_stop.
>>
>>> http://git.neil.brown.name/?p=md.git;a=commit;h=260fa034ef7a4ff8b73068b48ac497edd5217491
>>
>> BTW: It will be great if you could add my Reported-by and Tested-by:)
>
> Sorry I forgot those. To late to add them now.
>
Fine, Thanks all the time:)
Regards,
Jack
> NeilBrown
>
>
>
>>
>> Best regards,
>> Jack
>>
>
next prev parent reply other threads:[~2013-09-11 7:40 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
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 [this message]
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=52301E58.7010000@gmail.com \
--to=xjtuwjp@gmail.com \
--cc=jinpu.wang@profitbricks.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sebastian.riemer@profitbricks.com \
--cc=stable@vger.kernel.org \
/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.