From: NeilBrown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux RAID <linux-raid@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: PULL REQUEST - md updates for 3.4
Date: Mon, 19 Mar 2012 17:00:50 +1100 [thread overview]
Message-ID: <20120319170050.418d5fea@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 3014 bytes --]
The following changes since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7:
Linux 3.3 (2012-03-18 16:15:34 -0700)
are available in the git repository at:
git://neil.brown.name/md/ md-3.4
for you to fetch changes up to ecb178bb2b154a40cfae9fa4c42e62ccfa81ac6b:
md: Add judgement bb->unacked_exist in function md_ack_all_badblocks(). (2012-03-19 12:46:42 +1100)
----------------------------------------------------------------
(from the branch description for md-scratch local branch)
for-linus
md updates for 3.4
Mostly tidying up code in preparation for some bigger changes
next time.
A few bug fixes tagged for -stable.
Main functionality change is that some RAID10 arrays can now
grow to use extra space that may have been made available on the
individual devices.
----------------------------------------------------------------
NeilBrown (19):
md/raid5: make sure reshape_position is cleared on error path.
md/raid10: remove unnecessary smp_mb() from end_sync_write
md/raid5: removed unused 'added_devices' variable.
md: allow re-add to failed arrays.
md: don't set md arrays to readonly on shutdown.
md/bitmap: ensure to load bitmap when creating via sysfs.
md/raid1,raid10: avoid deadlock during resync/recovery.
md: tidy up rdev_for_each usage.
md: add proper merge_bvec handling to RAID0 and Linear.
md/raid10: handle merge_bvec_fn in member devices.
md/raid1: handle merge_bvec_fn in member devices.
md/raid10 - support resizing some RAID10 arrays.
md/bitmap: remove some unused noise from bitmap.h
md/bitmap: move printing of bitmap status to bitmap.c
md/bitmap: change a 'goto' to a normal 'if' construct.
md/bitmap: remove some pointless locking.
md/bitmap: remove unnecessary indirection when allocating.
md/bitmap: discard CHUNK_BLOCK_SHIFT macro
md: fix clearing of the 'changed' flags for the bad blocks list.
majianpeng (3):
md: Use existed macros instead of numbers
md/raid5: use atomic_dec_return() instead of atomic_dec() and atomic_read().
md: Add judgement bb->unacked_exist in function md_ack_all_badblocks().
drivers/md/bitmap.c | 152 ++++++++++++++++++------------------
drivers/md/bitmap.h | 22 +-----
drivers/md/dm-raid.c | 16 ++--
drivers/md/faulty.c | 2 +-
drivers/md/linear.c | 32 ++++----
drivers/md/md.c | 140 ++++++++++++++--------------------
drivers/md/md.h | 13 +++-
drivers/md/multipath.c | 2 +-
drivers/md/raid0.c | 164 ++++++++++++++++++++++------------------
drivers/md/raid0.h | 11 ++-
drivers/md/raid1.c | 98 ++++++++++++++++++------
drivers/md/raid10.c | 187 +++++++++++++++++++++++++++++++++------------
drivers/md/raid5.c | 25 +++----
include/linux/raid/md_p.h | 6 +-
14 files changed, 496 insertions(+), 374 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
reply other threads:[~2012-03-19 6:00 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=20120319170050.418d5fea@notabene.brown \
--to=neilb@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).