From: Alexander Lyakas <alex.bolshoy@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: commit backport request
Date: Fri, 13 Jul 2012 00:28:00 +0300 [thread overview]
Message-ID: <CAGRgLy4tBOS1B8raJmxoge1CaWc-18=c_fMe6E_oCqa1ntSHzQ@mail.gmail.com> (raw)
In-Reply-To: <20120712141422.05809022@notabene.brown>
Hi,
Is there any indication that can tell I am hitting this particular issue?
I think I hit something similar to that once, IOs were hang within a
raid5 and not returning. I issues w > sysrq-trigger and also have most
of the procfs/<pid> info, so is there something I can look at to
confirm?
On Thu, Jul 12, 2012 at 7:14 AM, NeilBrown <neilb@suse.de> wrote:
> On Wed, 11 Jul 2012 15:07:40 -0700 Greg KH <gregkh@linuxfoundation.org> wrote:
>
>> On Mon, Jul 09, 2012 at 02:02:30PM +1000, NeilBrown wrote:
>> >
>> > Hi Mr Stable,
>> >
>> > please apply patch
>> >
>> > commit fab363b5ff502d1b39ddcfec04271f5858d9f26e
>> > Author: Shaohua Li <shli@kernel.org>
>> > Date: Tue Jul 3 15:57:19 2012 +1000
>> >
>> > raid5: delayed stripe fix
>> >
>> >
>> > to 3.4.y and 3.2.y.
>> >
>> > It fixes a deadlock in RAID5 which can cause all IO to hang.
>> > It has been demonstrated to fix a real-life problem (the race is not
>> > theoretical).
>>
>> Is it also needed for 3.0.x? It seems to apply there just fine.
>
> Yes it is. Don't know why I missed that.
> I see you've already included it - thanks.
>
> NeilBrown
next prev parent reply other threads:[~2012-07-12 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 4:02 commit backport request NeilBrown
2012-07-09 5:08 ` Igor M Podlesny
2012-07-09 5:19 ` NeilBrown
2012-07-11 22:07 ` Greg KH
2012-07-12 4:14 ` NeilBrown
2012-07-12 21:28 ` Alexander Lyakas [this message]
2012-07-16 3:23 ` NeilBrown
2012-07-16 8:59 ` Alexander Lyakas
2012-07-12 3:52 ` Ben Hutchings
2012-07-17 3:26 ` Igor M Podlesny
2012-07-17 3:43 ` NeilBrown
2012-07-17 3:48 ` Ben Hutchings
2012-07-20 2:38 ` Igor M Podlesny
2012-07-20 2:58 ` NeilBrown
2012-07-20 6:35 ` Igor M Podlesny
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='CAGRgLy4tBOS1B8raJmxoge1CaWc-18=c_fMe6E_oCqa1ntSHzQ@mail.gmail.com' \
--to=alex.bolshoy@gmail.com \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).