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>, Shaohua Li <shli@fb.com>
Subject: [GIT PULL REQUEST] more md bug fixes for 4.1-rc
Date: Fri, 29 May 2015 16:20:13 +1000 [thread overview]
Message-ID: <20150529162013.437422e2@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
Hi Linus,
please pull these fixes.
I think raid5 is all working nicely again now.
I think there is still a race somewhere in starting the recovery thread, but
it is minor and I suspect I'll have it nailed soon. Not quite this week
though.
Thanks,
NeilBrown
The following changes since commit 8532e3439087de69bb1b71fd6be2baa6fc196a55:
md/bitmap: remove rcu annotation from pointer arithmetic. (2015-05-21 09:14:41 +1000)
are available in the git repository at:
git://neil.brown.name/md/ tags/md/4.1-rc5-fixes
for you to fetch changes up to 56ccc1125bc141cf63927eda7febff4216dea2d3:
md: fix race when unfreezing sync_action (2015-05-28 18:04:45 +1000)
----------------------------------------------------------------
Assorted fixes for new RAID5 stripe-batching functionality.
Unfortunately this functionality was merged a little prematurely.
The necessary testing and code review is now complete (or as
complete as it can be) and to code passes a variety of tests
and looks quite sensible.
Also a fix for some recent locking changes - a race was introduced
which causes a reshape request to sometimes fail. No data safety issues.
----------------------------------------------------------------
NeilBrown (10):
md/raid5: ensure whole batch is delayed for all required bitmap updates.
md/raid5: close race between STRIPE_BIT_DELAY and batching.
md/raid5: Ensure a batch member is not handled prematurely.
md/raid5: remove condition test from check_break_stripe_batch_list.
md/raid5: duplicate some more handle_stripe_clean_event code in break_stripe_batch_list
md/raid5: add handle_flags arg to break_stripe_batch_list.
md/raid5: be more selective about distributing flags across batch.
md/raid5: call break_stripe_batch_list from handle_stripe_clean_event
md/raid5: break stripe-batches when the array has failed.
md: fix race when unfreezing sync_action
drivers/md/md.c | 14 ++---
drivers/md/raid5.c | 146 +++++++++++++++++++++++++++++++----------------------
drivers/md/raid5.h | 5 +-
3 files changed, 98 insertions(+), 67 deletions(-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
reply other threads:[~2015-05-29 6: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=20150529162013.437422e2@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@fb.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).