From: Neil Brown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Vladimir Dronnikov <dronnikov@gmail.com>
Subject: [PULL REQUEST - resend] md fixes for 2.6.32
Date: Fri, 30 Oct 2009 14:15:26 +1100 [thread overview]
Message-ID: <19178.23118.321053.935200@notabene.brown> (raw)
Hi Linus,
please pull some md fixes for 2.6.32 as described below.
The main issues related to:
- The recently merged hardware offload for RAID6 calculations, which
didn't handle the DDF style properly, and
- The less recently added reshaping code that allows a RAID5 to be
reshaped to have fewer devices. Restarting such an array if it
was shutdown during the reshape did not work.
Also we remove a build-time dependency on perl.
Thanks,
NeilBrown
The following changes since commit 964fe080d94db82a3268443e9b9ece4c60246414:
Linus Torvalds (1):
Merge git://git.kernel.org/.../rusty/linux-2.6-for-linus
are available in the git repository at:
git://neil.brown.name/md/ for-linus
Dan Williams (6):
md/raid5: initialize conf->device_lock earlier
md/raid456: downlevel multicore operations to raid_run_ops
md/raid6: kill a gcc-4.0.1 'uninitialized variable' warning
async_pq: kill a stray dma_map() call and other cleanups
async_pq: rename scribble page
async_tx: fix asynchronous raid6 recovery for ddf layouts
NeilBrown (8):
Revert "md: do not progress the resync process if the stripe was blocked"
md/raid1/raid10: add a cond_resched
md: raid1/raid10: handle allocation errors during array setup.
md: remove clumsy usage of do_sync_mapping_range from bitmap code
md: fix problems with RAID6 calculations for DDF.
md: Fix handling of raid5 array which is being reshaped to fewer devices.
md/async: don't pass a memory pointer as a page pointer.
raid6/async_tx: handle holes in block list in async_syndrome_val
Vladimir Dronnikov (1):
md: drivers/md/unroll.pl replaced with awk analog
crypto/async_tx/async_pq.c | 60 +++++++-----
crypto/async_tx/async_raid6_recov.c | 100 +++++++++++++-------
crypto/async_tx/async_xor.c | 18 ++--
drivers/md/Makefile | 22 ++--
drivers/md/bitmap.c | 9 +-
drivers/md/md.c | 2 +-
drivers/md/raid1.c | 6 +-
drivers/md/raid10.c | 5 +-
drivers/md/raid5.c | 182 ++++++++++++++++++-----------------
drivers/md/raid5.h | 14 +++-
drivers/md/raid6altivec.uc | 2 +-
drivers/md/raid6int.uc | 2 +-
drivers/md/raid6test/Makefile | 42 ++++----
drivers/md/unroll.awk | 20 ++++
drivers/md/unroll.pl | 24 -----
15 files changed, 284 insertions(+), 224 deletions(-)
create mode 100644 drivers/md/unroll.awk
delete mode 100644 drivers/md/unroll.pl
reply other threads:[~2009-10-30 3:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19178.23118.321053.935200@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dronnikov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=torvalds@linux-foundation.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