From: NeilBrown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux RAID <linux-raid@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Alexander Lyakas <alex.bolshoy@gmail.com>,
Bassow Jonathan <jbrassow@redhat.com>,
majianpeng <majianpeng@gmail.com>
Subject: [GIT PULL REQUEST] late md/raid1 bug fixes for 3.17
Date: Wed, 24 Sep 2014 12:18:05 +1000 [thread overview]
Message-ID: <20140924121805.1b8c3bd9@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
Hi Linus,
it is amazing how much easier it is to find bugs when you know one is there.
Two bug reports resulted in finding 7 bugs!!
All are tagged for -stable. Those that can't cause (rare) data corruption,
cause lockups.
Thanks,
NeilBrown
The following changes since commit d030671f3f261e528dc6e396a13f10859a74ae7c:
Merge branch 'for-3.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2014-09-07 20:20:16 -0700)
are available in the git repository at:
git://git.neil.brown.name/md/ tags/md/3.17-more-fixes
for you to fetch changes up to b8cb6b4c121e1bf1963c16ed69e7adcb1bc301cd:
md/raid1: fix_read_error should act on all non-faulty devices. (2014-09-22 11:26:01 +1000)
----------------------------------------------------------------
Bugfixes for md/raid1
particularly, but not only, fixing new "resync" code.
----------------------------------------------------------------
NeilBrown (8):
md/raid1: intialise start_next_window for READ case to avoid hang
md/raid1: be more cautious where we read-balance during resync.
md/raid1: clean up request counts properly in close_sync()
md/raid1: make sure resync waits for conflicting writes to complete.
md/raid1: Don't use next_resync to determine how far resync has progressed
md/raid1: update next_resync under resync_lock.
md/raid1: count resync requests in nr_pending.
md/raid1: fix_read_error should act on all non-faulty devices.
drivers/md/raid1.c | 40 ++++++++++++++++++++++------------------
1 file changed, 22 insertions(+), 18 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2014-09-24 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 2:18 NeilBrown [this message]
2014-09-26 19:08 ` [GIT PULL REQUEST] late md/raid1 bug fixes for 3.17 BillStuff
2014-09-27 0:09 ` 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=20140924121805.1b8c3bd9@notabene.brown \
--to=neilb@suse.de \
--cc=alex.bolshoy@gmail.com \
--cc=jbrassow@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=majianpeng@gmail.com \
--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).