Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: NeilBrown <neilb@suse.de>
Cc: linux RAID <linux-raid@vger.kernel.org>
Subject: Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
Date: Mon, 31 Oct 2011 13:04:34 +0800	[thread overview]
Message-ID: <4EAE2C62.3030506@fnarfbargle.com> (raw)
In-Reply-To: <20111031130859.121d5620@notabene.brown>

On 31/10/11 10:08, NeilBrown wrote:
>
> Hi Linus et al,
>
>   I just discovered a fairly serious flaw that I introduced into 3.1 - details
>   below.
>
>   Anyone running RAID10 with 3.1 is advised to either apply this patch or
>   revert an earlier kernel as soon as possible.  In the mean time, remove any
>   hot spares from an RAID10 array.
>

G'day Neil,

Is that the issue I bumped up against here?

http://permalink.gmane.org/gmane.linux.raid/35805


  reply	other threads:[~2011-10-31  5:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31  2:08 PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare NeilBrown
2011-10-31  5:04 ` Brad Campbell [this message]
2011-10-31  5:34   ` Brad Campbell
2011-10-31  5:49     ` NeilBrown
2011-10-31  6:10       ` Brad Campbell

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=4EAE2C62.3030506@fnarfbargle.com \
    --to=lists2009@fnarfbargle.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