Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PULL-REQUEST]  3 md fixes suitable for 2.6.29 and -stable
Date: Wed, 25 Feb 2009 13:30:06 +1100	[thread overview]
Message-ID: <18852.44334.513936.123107@notabene.brown> (raw)


Hi Linus, 
 Recently discovered bugs, mostly affecting raid10 (though with a
 raid1 connection).
 Can cause Oops or data corruption.

Thanks,
NeilBrown



The following changes since commit 2ec77fc93ca8731368fbe8e71f805c0569d4bcee:
  Linus Torvalds (1):
        Merge branch 'drm-fixes' of git://git.kernel.org/.../airlied/drm-2.6

are available in the git repository at:

  git://neil.brown.name/md/ for-linus

NeilBrown (3):
      md/raid10:  Don't skip more than 1 bitmap-chunk at a time during recovery.
      md/raid10:  Don't call bitmap_cond_end_sync when we are doing recovery.
      md: avoid races when stopping resync.

 drivers/md/raid1.c  |    3 ++-
 drivers/md/raid10.c |   19 ++++++++++---------
 2 files changed, 12 insertions(+), 10 deletions(-)

                 reply	other threads:[~2009-02-25  2:30 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=18852.44334.513936.123107@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