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>,
Andrei Warkentin <andreiw@vmware.com>,
Damian Nowak <spam@nowaker.net>, Bruno Wolff III <bruno@wolff.to>,
majianpeng <majianpeng@gmail.com>,
Alexander Lyakas <alex.bolshoy@gmail.com>
Subject: [GIT PULL REQUEST] last minute md fixes for 3.13
Date: Wed, 15 Jan 2014 16:20:41 +1100 [thread overview]
Message-ID: <20140115162041.4ab345da@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Sorry they are late .... Christmas holidays and all that. Hopefully they can
still squeak into 3.13.
NeilBrown
The following changes since commit 6d183de4077191d1201283a9035ce57a9b05254d:
md/raid5: fix newly-broken locking in get_active_stripe. (2013-11-28 11:00:15 +1100)
are available in the git repository at:
git://neil.brown.name/md tags/md/3.13-fixes
for you to fetch changes up to 8313b8e57f55b15e5b7f7fc5d1630bbf686a9a97:
md: fix problem when adding device to read-only array with bitmap. (2014-01-14 16:44:08 +1100)
----------------------------------------------------------------
md: half a dozen bug fixes for 3.13
All of these fix real bugs the people have hit, and are tagged
for -stable.
----------------------------------------------------------------
NeilBrown (6):
md/raid5: Fix possible confusion when multiple write errors occur.
md/raid10: fix two bugs in handling of known-bad-blocks.
md/raid1: fix request counting bug in new 'barrier' code.
md/raid5: fix a recently broken BUG_ON().
md/raid10: fix bug when raid10 recovery fails to recover a block.
md: fix problem when adding device to read-only array with bitmap.
drivers/md/md.c | 18 +++++++++++++++---
drivers/md/md.h | 3 +++
drivers/md/raid1.c | 3 +--
drivers/md/raid10.c | 12 ++++++------
drivers/md/raid5.c | 7 ++++---
5 files changed, 29 insertions(+), 14 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
reply other threads:[~2014-01-15 5:20 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=20140115162041.4ab345da@notabene.brown \
--to=neilb@suse.de \
--cc=alex.bolshoy@gmail.com \
--cc=andreiw@vmware.com \
--cc=bruno@wolff.to \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=majianpeng@gmail.com \
--cc=spam@nowaker.net \
--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).