From: Michal Hocko <mhocko@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: L1TFv8
Date: Tue, 10 Jul 2018 15:25:20 +0200 [thread overview]
Message-ID: <20180710132520.GN14284@dhcp22.suse.cz> (raw)
In-Reply-To: <20180615194823.bjo72okfkohrxnf2@treble>
On Fri 15-06-18 14:48:23, speck for Josh Poimboeuf wrote:
> On Fri, Jun 15, 2018 at 04:50:38PM +0200, speck for Thomas Gleixner wrote:
> > On Wed, 13 Jun 2018, speck for Andi Kleen wrote:
> >
> > > This is v8 of the native OS patchkit to mitigate the L1TF side channel.
> > > It does not cover KVM.
> > >
> > > This version addresses the latest review feedbacks. The mitigation
> > > setup has been moved into check_bugs, and the memory size checking
> > > patch is now integrated into the standard setup. The swap mitigation
> > > has been split into two patches. Various other changes.
> > > For more details see the individual changelogs.
> >
> > I've picked up the whole set with a few edits and applied it to the master
> > branch of the speck git repository and backported it to the linux-4.17.y,
> > linux-4.16.y and linux-4.14.y branches.
> >
> > Git bundle against Linus tree is attached.
>
> Has anyone tested these patches on a multi-node system with NUMA
> balancing enabled? We've see some panics on RHEL because _PAGE_NUMA ==
> _PAGE_PROTNONE. Not sure if this problem also exists upstream.
>
> Andrea is looking into it (and I think he'll be joining this list
> shortly).
This didn't have any follow up but I guess you have figured out in the
meantime. So JFTR. We have encountered oopses on older 4.4 kernels
as well. And it turned out that fd7e315988b7 ("x86/mm: Simplify
p[g4um]d_page() macros") is really needed.
HTH
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-07-10 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180613224850.464286110D@crypto-ml.lab.linutronix.de>
2018-06-14 14:37 ` L1TFv8 Thomas Gleixner
2018-06-15 14:50 ` L1TFv8 Thomas Gleixner
2018-06-15 19:48 ` [MODERATED] L1TFv8 Josh Poimboeuf
2018-06-15 20:09 ` L1TFv8 Thomas Gleixner
2018-06-15 20:57 ` [MODERATED] L1TFv8 Andi Kleen
2018-06-15 21:50 ` Andi Kleen
2018-06-19 14:54 ` Michal Hocko
2018-06-20 16:04 ` Konrad Rzeszutek Wilk
2018-06-20 16:36 ` L1TFv8 Thomas Gleixner
2018-06-20 17:44 ` L1TFv8 Thomas Gleixner
2018-07-10 13:25 ` Michal Hocko [this message]
[not found] <20180613224846.B1FF561106@crypto-ml.lab.linutronix.de>
2018-06-14 2:56 ` [MODERATED] L1TFv8 Andi Kleen
2018-06-29 9:21 ` Jon Masters
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=20180710132520.GN14284@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=speck@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).