linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 0 of 6] Introduction
Date: Mon, 07 Feb 2005 13:44:19 +1100	[thread overview]
Message-ID: <20050207133555.17870.patches@notabene> (raw)


Following are 6 patches for md in 2.6.11-rc2-mm2

I believe they are all suitable for inclusion in 2.6.11

- Fix silly bugs in version-1 superblock code (which currently is 
   not widely used)
- Fix possible Oops in raid_set_faulty (which is hard to trigger in 
   normal usage)
- Make md work better with devfs when it is compiled in.
- Fix a possible endless-resync-loop
- Removing the for loop in "copy_data" (raid5 and raid6) which caused 
  some copinging to be done multiple times (should be harmless, but is 
  a waste)
- Fix handling for overlapping requests to raid5 and raid6.  -mm currently
  has a patch which is even more broken than the original code.  Adding
  this patch fixes it up.

Thanks,
NeilBrown

             reply	other threads:[~2005-02-07  2:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07  2:44 NeilBrown [this message]
2005-02-07  2:44 ` [PATCH md 4 of 6] Fix endless loop when syncing an array that doesn't need any resync NeilBrown
2005-02-07  2:44 ` [PATCH md 2 of 6] Prevent oops when drive set faulty in inactive md array NeilBrown
2005-02-07  2:44 ` [PATCH md 5 of 6] Remove extra loop from copy_data NeilBrown
2005-02-07  2:44 ` [PATCH md 3 of 6] Make md work a bit better with devfs NeilBrown
2005-02-07  2:44 ` [PATCH md 6 of 6] Fix handling of overlapping requests in raid5 NeilBrown
2005-02-08  2:24   ` Andrew Morton
2005-02-08  2:39     ` Neil Brown
2005-02-08  3:07       ` Andrew Morton
2005-02-07  2:44 ` [PATCH md 1 of 6] Fix problems with verion-1 superblock code NeilBrown

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=20050207133555.17870.patches@notabene \
    --to=neilb@cse.unsw.edu.au \
    --cc=akpm@osdl.org \
    --cc=linux-raid@vger.kernel.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).