Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux RAID <linux-raid@vger.kernel.org>,
	Ian Kumlien <ian.kumlien@gmail.com>,
	Ethan Wilson <ethan.wilson@shiftmail.org>,
	Nicolas Schichan <nschichan@freebox.fr>,
	Richard Michael <rmichael@edgeofthenet.org>,
	Andrei Warkentin <andreiw@vmware.com>
Subject: [GIT PULL REQUEST] md updates for 3.14
Date: Fri, 24 Jan 2014 12:09:29 +1100	[thread overview]
Message-ID: <20140124120929.1807f12b@notabene.brown> (raw)

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


Hi Linus,
 just a few bugfixes for md.

The following changes since commit 8313b8e57f55b15e5b7f7fc5d1630bbf686a9a97:

  md: fix problem when adding device to read-only array with bitmap. (2014-01-14 16:44:08 +1100)

are available in the git repository at:

  git://neil.brown.name/md tags/md/3.14

for you to fetch changes up to 7da9d450ab2843bf1db378c156acc6304dbc1c2b:

  md/raid5: close recently introduced race in stripe_head management. (2014-01-22 11:45:03 +1100)

----------------------------------------------------------------
md updates for 3.14

All bug fixes, two tagged for -stable.

----------------------------------------------------------------
NeilBrown (6):
      md: Change handling of save_raid_disk and metadata update during recovery.
      md: allow a partially recovered device to be hot-added to an array.
      md/raid10: avoid fullsync when not necessary.
      md: ensure metadata is writen after raid level change.
      md/raid5: fix long-standing problem with bitmap handling on write failure.
      md/raid5: close recently introduced race in stripe_head management.

Nicolas Schichan (1):
      md: check command validity early in md_ioctl().

 drivers/md/md.c                | 76 +++++++++++++++++++++++++++++++-----------
 drivers/md/raid10.c            |  3 +-
 drivers/md/raid5.c             |  9 ++---
 include/uapi/linux/raid/md_p.h |  6 +++-
 4 files changed, 68 insertions(+), 26 deletions(-)

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

                 reply	other threads:[~2014-01-24  1:09 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=20140124120929.1807f12b@notabene.brown \
    --to=neilb@suse.de \
    --cc=andreiw@vmware.com \
    --cc=ethan.wilson@shiftmail.org \
    --cc=ian.kumlien@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=nschichan@freebox.fr \
    --cc=rmichael@edgeofthenet.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