From: Corey Minyard <minyard@acm.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>
Subject: [GIT PULL] IPMI serious bugfixes for 5.0
Date: Wed, 23 Jan 2019 11:28:37 -0600 [thread overview]
Message-ID: <200450ff-49dd-da74-53b6-b0a0d71b4c8a@acm.org> (raw)
The following changes since commit 7b55851367136b1efd84d98fea81ba57a98304cf:
fork: record start_time late (2019-01-08 09:40:53 -0800)
are available in the Git repository at:
https://github.com/cminyard/linux-ipmi.git tags/for-linus-5.0
for you to fetch changes up to 913a89f009d98c85a902d718cd54bb32ab11d167:
ipmi: Don't initialize anything in the core until something uses it
(2019-01-23 11:09:32 -0600)
----------------------------------------------------------------
I missed the merge window, which wasn't really important at the time
as there was nothing that critical that I had for 5.0.
However, I say that,and then a number of critical fixes come in:
ipmi: fix use-after-free of user->release_barrier.rda
ipmi: Prevent use-after-free in deliver_response
ipmi: msghandler: Fix potential Spectre v1 vulnerabilities
which are obvious candidates for 5.0. Then there is:
ipmi:ssif: Fix handling of multi-part return messages
which is less critical, but it still has some off-by-one things that
are not great, so it seemed appropriate. Some machines are broken
without it. Then:
ipmi: Don't initialize anything in the core until something uses it
It turns out that using SRCU causes large chunks of memory to be used
on big iron machines, even if IPMI is never used. This was causing
some issues for people on those machines.
Everything here is destined for stable.
----------------------------------------------------------------
Corey Minyard (2):
ipmi:ssif: Fix handling of multi-part return messages
ipmi: Don't initialize anything in the core until something uses it
Fred Klassen (1):
ipmi: Prevent use-after-free in deliver_response
Gustavo A. R. Silva (1):
ipmi: msghandler: Fix potential Spectre v1 vulnerabilities
Yang Yingliang (1):
ipmi: fix use-after-free of user->release_barrier.rda
drivers/char/ipmi/ipmi_msghandler.c | 173
+++++++++++++++++++++---------------
drivers/char/ipmi/ipmi_ssif.c | 25 ++++--
2 files changed, 117 insertions(+), 81 deletions(-)
next reply other threads:[~2019-01-23 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 17:28 Corey Minyard [this message]
2019-01-23 20:30 ` pr-tracker-bot
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=200450ff-49dd-da74-53b6-b0a0d71b4c8a@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®