From: NeilBrown <neilb@suse.com>
To: Shaohua Li <shli@kernel.org>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
David R <david@unsolicited.net>,
linux-raid@vger.kernel.org
Subject: [md PATCH 0/2] Fix two bug in the new write_pending counting.
Date: Tue, 08 Aug 2017 16:56:36 +1000 [thread overview]
Message-ID: <150217527795.23065.7747775748038187816.stgit@noble> (raw)
Two separate bugs caused by the same patch.
One causes a hard lockup that was reported on the list.
Other found by inspection.
Both suitable for -stable.
Please review the second one closely. I think it is correct now, but
then I thought it was correct before too :-(
Thanks,
NeilBrown
---
NeilBrown (2):
md: always clear ->safemode when md_check_recovery gets the mddev lock.
md: fix test in md_write_start()
drivers/md/md.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
Signature
next reply other threads:[~2017-08-08 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 6:56 NeilBrown [this message]
2017-08-08 6:56 ` [md PATCH 1/2] md: always clear ->safemode when md_check_recovery gets the mddev lock NeilBrown
2017-08-08 14:40 ` Shaohua Li
2017-08-08 6:56 ` [md PATCH 2/2] md: fix test in md_write_start() 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=150217527795.23065.7747775748038187816.stgit@noble \
--to=neilb@suse.com \
--cc=david@unsolicited.net \
--cc=linux-raid@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=shli@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