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>
Subject: [PULL REQUEST] md: a couple of minor bug fixes, and one serious bug fixed.
Date: Tue, 24 Apr 2012 10:57:42 +1000	[thread overview]
Message-ID: <20120424105742.57cefab7@notabene.brown> (raw)

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


Hi Linus,
 please pull the following for the next -rc.

Thanks,
NeilBrown


The following changes since commit afbaa90b80b1ec66e5137cc3824746bfdf559b18:

  md/bitmap: prevent bitmap_daemon_work running while initialising bitmap (2012-04-12 16:05:06 +1000)

are available in the git repository at:

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

for you to fetch changes up to 30b8aa9172dfeaac6d77897c67ee9f9fc574cdbb:

  md: fix possible corruption of array metadata on shutdown. (2012-04-24 10:23:16 +1000)

----------------------------------------------------------------
md: a few more bug fixes for 3.4

2 are tagged for -stable, one being for a fairly serious bug
that can corrupt metadata and make it hard to recovery an array.
The other is for a more recent regression since 3.3

----------------------------------------------------------------
Jonathan Brassow (1):
      DM RAID: Use safe version of rdev_for_each

NeilBrown (2):
      md: don't call ->add_disk unless there is good reason.
      md: fix possible corruption of array metadata on shutdown.

 drivers/md/dm-raid.c |    4 ++--
 drivers/md/md.c      |    7 ++++---
 2 files changed, 6 insertions(+), 5 deletions(-)

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

                 reply	other threads:[~2012-04-24  0:57 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=20120424105742.57cefab7@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).