From: Bill Davidsen <davidsen@tmr.com>
To: NeilBrown <neilb@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH 000 of 6] md: Assorted fixes and features for md for 2.6.21
Date: Tue, 20 Feb 2007 18:22:36 -0500 [thread overview]
Message-ID: <45DB82BC.60805@tmr.com> (raw)
In-Reply-To: <20070220172544.15678.patches@notabene>
NeilBrown wrote:
> Following 6 patches are against 2.6.20 and are suitable for 2.6.21.
> They are not against -mm because the new plugging makes raid5 not work
> and so not testable, and there are a few fairly minor intersections between
> these patches and those patches.
> There is also a very minor conflict with the hardware-xor patches - one line
> of context is different.
>
> Patch 1 should probably go in -stable - the bug could cause data
> corruption in a fairly uncommon raid10 configuration, so that one and
> this intro are Cc:ed to stable@kernel.org.
>
> Thanks,
> NeilBrown
>
>
> [PATCH 001 of 6] md: Fix raid10 recovery problem.
> [PATCH 002 of 6] md: RAID6: clean up CPUID and FPU enter/exit code
> [PATCH 003 of 6] md: Move warning about creating a raid array on partitions of the one device.
> [PATCH 004 of 6] md: Clean out unplug and other queue function on md shutdown
> [PATCH 005 of 6] md: Restart a (raid5) reshape that has been aborted due to a read/write error.
> [PATCH 006 of 6] md: Add support for reshape of a raid6
Every month or so there are a bunch of patches like this, which do
various enhancements to the kernel. And these are usually based against
the release kernel, and all is fine. But every once in a while there is
a patch which is more urgent, in this case the RAID10 one, which is
really desirable to get into every kernel running on a machine. Are
patches marked as needed for -stable also fast tracked to -git inclusion?
If this isn't in -git14 I'm going to rebuild with it before testing
Neil's NFS stuff. The NFS server test data is on RAID10 ;-)
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-02-20 23:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 6:34 [PATCH 000 of 6] md: Assorted fixes and features for md for 2.6.21 NeilBrown
2007-02-20 6:34 ` [PATCH 001 of 6] md: Fix raid10 recovery problem NeilBrown
2007-02-20 6:34 ` [PATCH 002 of 6] md: RAID6: clean up CPUID and FPU enter/exit code NeilBrown
2007-02-20 6:35 ` [PATCH 003 of 6] md: Move warning about creating a raid array on partitions of the one device NeilBrown
2007-02-20 6:35 ` [PATCH 004 of 6] md: Clean out unplug and other queue function on md shutdown NeilBrown
2007-02-20 6:35 ` [PATCH 005 of 6] md: Restart a (raid5) reshape that has been aborted due to a read/write error NeilBrown
2007-02-20 6:35 ` [PATCH 006 of 6] md: Add support for reshape of a raid6 NeilBrown
2007-02-21 22:48 ` Andrew Morton
2007-02-21 23:36 ` Oleg Verych
2007-02-21 23:58 ` Andrew Morton
2007-02-21 23:57 ` Rafael J. Wysocki
2007-02-22 2:39 ` Neil Brown
2007-02-22 2:57 ` Andrew Morton
2007-02-23 12:15 ` Helge Hafting
2007-02-23 15:52 ` Bill Davidsen
2007-02-20 23:22 ` Bill Davidsen [this message]
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=45DB82BC.60805@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stable@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 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).