public inbox for linux-raid@vger.kernel.org
 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] md - various fixed for 2.6.30
Date: Tue, 26 May 2009 13:06:32 +1000	[thread overview]
Message-ID: <18971.23736.279996.704625@notabene.brown> (raw)


Hi Linus,
 a few more md fixes turned up through on going testing.

 A couple involve refining the user-space interface (sysfs) so that
 some of the recent features can be used reliably.

 The 'bitmap' fix isn't strictly a bug fix, but is reduces a fair
 amount of CPU wastage.

 The "don't use locked_ioctl" patch is again strictly not a bug fix,
 but it is so trivial it didn't seem worth leaving it for .31.
 It just tells the block layer that md doesn't need lock_kernel, even
 for ioctls.

Thanks,
NeilBrown


The following changes since commit 59a3759d0fe8d969888c741bb33f4946e4d3750d:
  Linus Torvalds (1):
        Linux 2.6.30-rc7

are available in the git repository at:

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

NeilBrown (7):
      md: always update level / chunk_size / layout when writing v1.x metadata.
      md: improve errno return when setting array_size
      md: bitmap: improve bitmap maintenance code.
      md: export 'frozen' resync state through sysfs
      md: raid5: avoid sector values going negative when testing reshape progress.
      md: don't update curr_resync_completed without also updating reshape_position.
      md: don't use locked_ioctl.

 drivers/md/bitmap.c |   13 +++++++------
 drivers/md/md.c     |   31 +++++++++++++++++++++----------
 drivers/md/raid5.c  |    6 +++---
 3 files changed, 31 insertions(+), 19 deletions(-)

                 reply	other threads:[~2009-05-26  3:06 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=18971.23736.279996.704625@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