From: NeilBrown <neilb@suse.com>
To: stable@vger.kernel.org
Subject: [PATCH 0/2] md patches for 3.1-stable
Date: Thu, 24 Sep 2015 11:48:11 +1000 [thread overview]
Message-ID: <20150924014803.4229.55633.stgit@noble> (raw)
Hi,
upstream patches:
Commit: 2d5b569b665e ("md/raid5: avoid races when changing cache size.")
Commit: 49895bcc7e56 ("md/raid5: don't let shrink_slab shrink too far.")
were tagged for -stable, but with a request they be delayed a bit:
Cc: stable@vger.kernel.org (4.1 - please delay until 2 weeks after release of 4.2)
Cc: stable@vger.kernel.org (4.1 - please release with 2d5b569b665)
Those two weeks have now passed but they didn't make it into 4.1.8.
I checked and the first patch has an easily resolved conflict. So to
make it as easy as possible the two patches based on 4.1.8 follow this
email.
Thanks,
NeilBrown
---
NeilBrown (2):
md/raid5: avoid races when changing cache size.
md/raid5: don't let shrink_slab shrink too far.
drivers/md/raid5.c | 34 +++++++++++++++++++++++++++-------
drivers/md/raid5.h | 3 ++-
2 files changed, 29 insertions(+), 8 deletions(-)
--
Signature
next reply other threads:[~2015-09-24 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 1:48 NeilBrown [this message]
2015-09-24 1:48 ` [PATCH 1/2] md/raid5: avoid races when changing cache size NeilBrown
2015-09-24 1:48 ` [PATCH 2/2] md/raid5: don't let shrink_slab shrink too far NeilBrown
2015-09-24 23:39 ` [PATCH 0/2] md patches for 3.1-stable Greg KH
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=20150924014803.4229.55633.stgit@noble \
--to=neilb@suse.com \
--cc=stable@vger.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