From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 000 of 4] Introduction
Date: Tue, 10 May 2005 15:04:02 +1000 [thread overview]
Message-ID: <20050510145931.1553.patches@notabene> (raw)
Hi Andrew,
Following are 4 patches for md in 2.6.12-rc3-mm3
The first is appropriate for 2.6.12 - it fixes a potential data corruption
with linear arrays (which was notice under XFS which does journal writes with
interesting alignments I think).
The second fixes an unlikely-to-hit-in-real-life bug where if an array fails
to be assembled properly, an oops maybe could eventuate.
The last two relate to bitmap intent logging and so depend on the other
related patches in -mm.
I think this bitmap stuff should be ready to go to Linus as soon as 2.6.12 is out.
Thanks,
NeilBrown
[PATCH md 001 of 4] Fix spliting of md/linear request that cross a device boundary
[PATCH md 002 of 4] Set the unplug_fn and issue_flush_fn for md devices *after* committed to creation.
[PATCH md 003 of 4] Two small fixes for md verion-1 superblocks.
[PATCH md 004 of 4] Make sure md/bitmap doesn't try to write a page with active writeback
next reply other threads:[~2005-05-10 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 5:04 NeilBrown [this message]
2005-05-10 5:04 ` [PATCH md 002 of 4] Set the unplug_fn and issue_flush_fn for md devices *after* committed to creation NeilBrown
2005-05-10 5:04 ` [PATCH md 004 of 4] Make sure md/bitmap doesn't try to write a page with active writeback NeilBrown
2005-05-10 5:04 ` [PATCH md 001 of 4] Fix spliting of md/linear request that cross a device boundary NeilBrown
2005-05-10 5:04 ` [PATCH md 003 of 4] Two small fixes for md verion-1 superblocks 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=20050510145931.1553.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