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,
	dm-devel@redhat.com
Subject: [PULL REQUEST] md updates for 2.6.36
Date: Sun, 8 Aug 2010 21:44:15 +1000	[thread overview]
Message-ID: <19550.39055.227259.954794@notabene.brown> (raw)


Hi Linus,
 here is my merge-window pull request for md.
 The bulk of this update is changes to allow md/raid5 to be plugged
 into dm as a dm target.  The changes to dm to make this happen are
 with the dm maintainer who has given in-principle agreement - they
 just need to be carefully reviewed.

 The remainder are some deadlock fixes which are tagged for -stable,
 one of which should have been around for quite some time, but have
 only manifested recently for some strange reason.

Thanks,
NeilBrown


The following changes since commit 9fe6206f400646a2322096b56c59891d530e8d51:

  Linux 2.6.35 (2010-08-01 15:11:14 -0700)

are available in the git repository at:
  git://neil.brown.name/md/ for-linus

Dan Williams (1):
      md: move revalidate_disk() back outside open_mutex

NeilBrown (21):
      md: reduce dependence on sysfs.
      md/raid5: factor out code for changing size of stripe cache.
      md/raid5: ensure we create a unique name for kmem_cache when mddev has no gendisk
      md: be more careful setting MD_CHANGE_CLEAN
      md: split out md_rdev_init
      md: export various start/stop interfaces
      md: add support for raising dm events.
      raid5: Don't set read-ahead when there is no queue
      md/raid5: export is_congested test
      md/raid5: add simple plugging infrastructure.
      md/plug: optionally use plugger to unplug an array during resync/recovery.
      md/raid5: export raid5 unplugging interface.
      md/bitmap: white space clean up and similar.
      md/bitmap: reduce dependence on sysfs.
      md/bitmap: clean up plugging calls.
      md/bitmap: optimise scanning of empty bitmaps.
      md/bitmap: prepare for storing write-intent-bitmap via dm-dirty-log.
      md/bitmap:  separate out loading a bitmap from initialising the structures.
      md/raid10: fix deadlock with unaligned read during resync
      md: fix another deadlock with removing sysfs attributes.
      md: clean up do_md_stop

 drivers/md/bitmap.c |  508 ++++++++++++++++++++++++++++-----------------------
 drivers/md/bitmap.h |    6 +
 drivers/md/md.c     |  286 ++++++++++++++++++-----------
 drivers/md/md.h     |   55 ++++++-
 drivers/md/raid10.c |   18 ++
 drivers/md/raid5.c  |  168 ++++++++++-------
 drivers/md/raid5.h  |    9 +-
 7 files changed, 643 insertions(+), 407 deletions(-)

                 reply	other threads:[~2010-08-08 11:44 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=19550.39055.227259.954794@notabene.brown \
    --to=neilb@suse.de \
    --cc=dm-devel@redhat.com \
    --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