From: Greg KH <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 5.1.2
Date: Tue, 14 May 2019 20:07:43 +0200 [thread overview]
Message-ID: <20190514180743.GA13519@kroah.com> (raw)
In-Reply-To: <20190514180424.GA11131@kroah.com>
On Tue, May 14, 2019 at 08:04:24PM +0200, Greg KH wrote:
> I'm announcing the release of the 5.1.2 kernel.
>
> All users of the 5.1 kernel series must upgrade. Well, kind of, let me rephrase that...
>
> All users of Intel processors made since 2011 must upgrade.
>
> Note, this release, and the other stable releases that are all being
> released right now at the same time, just went out all contain patches
> that have only seen the "public eye" for about 5 minutes. So be
> forwarned, they might break things, they might not build, but hopefully
> they fix things. Odds are we will be fixing a number of small things in
> this area for the next few weeks as things shake out on real hardware
> and workloads. So don't think you are done updating your kernel, you
> never are done with that :)
>
> As for what specifically these changes fix, I'll let the tech news sites
> fill you in on the details. Or go read the excellently written Xen
> Security Advisory 297:
> https://xenbits.xen.org/xsa/advisory-297.html
> That should give you a good idea of what a number of people have been
> dealing with for many many many months now.
Also see the new in-kernel documentation for how to handle all of this:
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html
next prev parent reply other threads:[~2019-05-14 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 18:04 Greg KH
2019-05-14 18:04 ` Greg KH
2019-05-14 18:07 ` Greg KH [this message]
2019-05-14 22:19 ` Bhaskar Chowdhury
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=20190514180743.GA13519@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--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®