From: Greg KH <gregkh@linuxfoundation.org>
To: "Matthias B." <matthias@winterdrache.de>,
Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to report kernel panic in 4.4.x
Date: Fri, 24 Aug 2018 21:18:48 +0200 [thread overview]
Message-ID: <20180824191848.GB15489@kroah.com> (raw)
In-Reply-To: <20180824181919.36e6b3c7@ninja>
On Fri, Aug 24, 2018 at 06:19:19PM +0200, Matthias B. wrote:
> Bisect identified the problem. It's the attached patch. I applied it to
> 4.4.152 with patch -Rp1 and I'm running the resulting kernel now.
>
> MSB
>
> --
> For every idiot-proof system there exists at least one system-proof
> idiot.
>
> >From 02ff2769edbce2261e981effbc3c4b98fae4faf0 Mon Sep 17 00:00:00 2001
> From: Andi Kleen <ak@linux.intel.com>
> Date: Tue, 7 Aug 2018 15:09:39 -0700
> Subject: [PATCH] x86/mm/pat: Make set_memory_np() L1TF safe
>
> commit 958f79b9ee55dfaf00c8106ed1c22a2919e0028b upstream
>
> set_memory_np() is used to mark kernel mappings not present, but it has
> it's own open coded mechanism which does not have the L1TF protection of
> inverting the address bits.
>
> Replace the open coded PTE manipulation with the L1TF protecting low level
> PTE routines.
>
> Passes the CPA self test.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> [ dwmw2: Pull in pud_mkhuge() from commit a00cc7d9dd, and pfn_pud() ]
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> [groeck: port to 4.4]
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> arch/x86/include/asm/pgtable.h | 27 +++++++++++++++++++++++++++
> arch/x86/mm/pageattr.c | 8 ++++----
> 2 files changed, 31 insertions(+), 4 deletions(-)
<snip>
Guenter, another report of this patch causing an issue. Any ideas? I
am away from test systems this weekend, but can push out patches if
needed.
thanks,
greg k-h
prev parent reply other threads:[~2018-08-24 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 12:24 Matthias B.
2018-08-24 12:59 ` Greg KH
2018-08-24 14:09 ` Matthias B.
2018-08-24 14:11 ` Greg KH
2018-08-24 14:24 ` Matthias B.
[not found] ` <20180824154344.1c53a68c@ninja>
2018-08-24 14:12 ` Greg KH
2018-08-24 14:33 ` Matthias B.
2018-08-24 15:55 ` Greg KH
2018-08-24 16:19 ` Matthias B.
2018-08-24 19:18 ` Greg KH [this message]
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=20180824191848.GB15489@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias@winterdrache.de \
--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
all inboxes | Powered by JetHome®