From: NeilBrown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux RAID <linux-raid@vger.kernel.org>,
Nate Dailey <nate.dailey@stratus.com>,
Jes Sorensen <Jes.Sorensen@redhat.com>,
Manibalan P <pmanibalan@amiindia.co.in>
Subject: [GIT PULL REQUEST] some more bugfixes for md.
Date: Wed, 18 Feb 2015 12:31:46 +1100 [thread overview]
Message-ID: <20150218123146.7424b524@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
hi Linus,
Please pull these three fixes, one tagged for -stable.
Thanks,
NeilBrown
The following changes since commit 53a6ab4d3f6d6dc87ec8f14998b4b5536ee2968c:
md/raid10: fix conversion from RAID0 to RAID10 (2015-02-12 14:09:57 +1100)
are available in the git repository at:
git://neil.brown.name/md/ tags/md/3.20-fixes
for you to fetch changes up to 26ac107378c4742978216be1005b7291b799c7b2:
md/raid5: Fix livelock when array is both resyncing and degraded. (2015-02-18 11:35:14 +1100)
----------------------------------------------------------------
3 bug md fixes for 3.20
yet-another-livelock in raid5, and a problem with write errors
to 4K-block devices.
----------------------------------------------------------------
Nate Dailey (1):
md/raid1: round up to bdev_logical_block_size in narrow_write_error
NeilBrown (2):
md/raid10: round up to bdev_logical_block_size in narrow_write_error.
md/raid5: Fix livelock when array is both resyncing and degraded.
drivers/md/raid1.c | 3 ++-
drivers/md/raid10.c | 3 ++-
drivers/md/raid5.c | 3 ++-
3 files changed, 6 insertions(+), 3 deletions(-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
reply other threads:[~2015-02-18 1:31 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=20150218123146.7424b524@notabene.brown \
--to=neilb@suse.de \
--cc=Jes.Sorensen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=nate.dailey@stratus.com \
--cc=pmanibalan@amiindia.co.in \
--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;
as well as URLs for NNTP newsgroup(s).