linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Shaohua Li <shli@fusionio.com>,
	Alexander Lyakas <alex.bolshoy@gmail.com>,
	majianpeng <majianpeng@gmail.com>,
	Christian Balzer <chibi@gol.com>
Subject: [PULL REQUEST] md fixes for 3.5-rc
Date: Tue, 3 Jul 2012 17:53:47 +1000	[thread overview]
Message-ID: <20120703175347.4d11f8e0@notabene.brown> (raw)

[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]


Hi Linus,
 please pull a pile of patches.

Thanks,
NeilBrown

The following changes since commit 6b16351acbd415e66ba16bf7d473ece1574cf0bc:

  Linux 3.5-rc4 (2012-06-24 12:53:04 -0700)

are available in the git repository at:

  git://neil.brown.name/md tags/md-3.5-fixes

for you to fetch changes up to b357f04a67c2aeee828b240863cd3f21d6cb3179:

  md: fix up plugging (again). (2012-07-03 17:45:31 +1000)

----------------------------------------------------------------
md: collection of bug fixes for 3.5

You go away for 2 weeks vacation and what do you get when you come back?
Piles of bugs :-)

Some found by inspection, some by testing, some during use in the field,
and some while developing for the next window...

----------------------------------------------------------------
NeilBrown (8):
      md/raid10: Don't try to recovery unmatched (and unused) chunks.
      md/raid5: prefer replacing failed devices over want-replacement devices.
      md/raid5: fix refcount problem when blocked_rdev is set.
      md/raid10: fix failure when trying to repair a read error.
      md: make 'name' arg to md_register_thread non-optional.
      md/raid1: fix bug in read_balance introduced by hot-replace
      md: support re-add of recovering devices.
      md: fix up plugging (again).

Shaohua Li (1):
      raid5: delayed stripe fix

majianpeng (4):
      md/raid5: Do not add data_offset before call to is_badblock
      md/raid5: In ops_run_io, inc nr_pending before calling md_wait_for_blocked_rdev
      md:Add blk_plug in sync_thread.
      md/raid456: When read error cannot be recovered, record bad block

 drivers/md/md.c        |    8 +++---
 drivers/md/multipath.c |    3 ++-
 drivers/md/raid1.c     |   13 ++++------
 drivers/md/raid10.c    |   26 +++++++++++--------
 drivers/md/raid5.c     |   67 +++++++++++++++++++++++++++++++++---------------
 5 files changed, 75 insertions(+), 42 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

             reply	other threads:[~2012-07-03  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  7:53 NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-05 23:01 [PULL REQUEST] md fixes for 3.5-rc NeilBrown

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=20120703175347.4d11f8e0@notabene.brown \
    --to=neilb@suse.de \
    --cc=alex.bolshoy@gmail.com \
    --cc=chibi@gol.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=majianpeng@gmail.com \
    --cc=shli@fusionio.com \
    --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).