From: NeilBrown <neilb@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-raid <linux-raid@vger.kernel.org>,
Tomas Papan <tomas.papan@gmail.com>,
Benjamin Randazzo <benjamin@randazzo.fr>,
Josh Boyer <jwboyer@fedoraproject.org>,
Alexander Lyakas <alex.bolshoy@gmail.com>
Subject: [GIT PULL REQUEST] md updates for 4.2-rc
Date: Wed, 5 Aug 2015 08:10:22 +1000 [thread overview]
Message-ID: <20150805081022.0ee9dac5@noble> (raw)
One of these patches is for a CVE: CVE-2015-5697
I'm not convinced it is serious (data leak from CAP_SYS_ADMIN ioctl)
but as people seem to want to back-port it, I've included a minimal
version here. The remainder of that patch from Benjamin is
code-cleanup and will arrive in the 4.3 merge window.
NeilBrown
The following changes since commit 74d33293e467df61de1b1d8b2fbe29e550dec33b:
Linux 4.2-rc5 (2015-08-02 18:34:55 -0700)
are available in the git repository at:
git://neil.brown.name/md/ tags/md/4.2-rc5-fixes
for you to fetch changes up to 49895bcc7e566ba455eb2996607d6fbd3447ce16:
md/raid5: don't let shrink_slab shrink too far. (2015-08-03 17:10:56
+1000)
----------------------------------------------------------------
Three more fixes for md in 4.2
Mostly corner-case stuff.
----------------------------------------------------------------
Benjamin Randazzo (1):
md: use kzalloc() when bitmap is disabled
NeilBrown (2):
md/raid1: extend spinlock to protect raid1_end_read_request
against inconsistencies
md/raid5: don't let shrink_slab shrink too far.
drivers/md/md.c | 2 +-
drivers/md/raid1.c | 10 ++++++----
drivers/md/raid5.c | 5 +++--
3 files changed, 10 insertions(+), 7 deletions(-)
reply other threads:[~2015-08-04 22:10 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=20150805081022.0ee9dac5@noble \
--to=neilb@suse.com \
--cc=alex.bolshoy@gmail.com \
--cc=benjamin@randazzo.fr \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=tomas.papan@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).