From: Sasha Levin <sashal@kernel.org>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: gregkh@linuxfoundation.org, luto@kernel.org, tglx@linutronix.de,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/mm: Move LDT remap out of KASLR region on 5-level paging" failed to apply to 4.18-stable tree
Date: Sat, 24 Nov 2018 10:57:52 -0500 [thread overview]
Message-ID: <20181124155752.GV1917@sasha-vm> (raw)
In-Reply-To: <20181124155327.GP1917@sasha-vm>
On Sat, Nov 24, 2018 at 10:53:27AM -0500, Sasha Levin wrote:
>On Fri, Nov 23, 2018 at 02:53:21PM +0300, Kirill A. Shutemov wrote:
>>On Mon, Nov 19, 2018 at 12:23:51PM +0000, gregkh@linuxfoundation.org wrote:
>>>
>>>The patch below does not apply to the 4.18-stable tree.
>>>If someone wants it applied there, or to any other stable or longterm
>>>tree, then please email the backport, including the original git commit
>>>id to <stable@vger.kernel.org>.
>>
>>>From b413460931ab36e958ee127522653cd16f7a248c Mon Sep 17 00:00:00 2001
>>From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
>>Date: Fri, 26 Oct 2018 15:28:54 +0300
>>Subject: [PATCH 1/2] x86/mm: Move LDT remap out of KASLR region on 5-level
>>paging
>>
>>commit d52888aa2753e3063a9d3a0c9f72f94aa9809c15 upstream
>>
>>On 5-level paging the LDT remap area is placed in the middle of the KASLR
>>randomization region and it can overlap with the direct mapping, the
>>vmalloc or the vmap area.
>>
>>The LDT mapping is per mm, so it cannot be moved into the P4D page table
>>next to the CPU_ENTRY_AREA without complicating PGD table allocation for
>>5-level paging.
>>
>>The 4 PGD slot gap just before the direct mapping is reserved for
>>hypervisors, so it cannot be used.
>>
>>Move the direct mapping one slot deeper and use the resulting gap for the
>>LDT remap area. The resulting layout is the same for 4 and 5 level paging.
>>
>>[ tglx: Massaged changelog ]
>>
>>Fixes: f55f0501cbf6 ("x86/pti: Put the LDT in its own PGD if PTI is on")
>>Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>>Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>>Reviewed-by: Andy Lutomirski <luto@kernel.org>
>>Cc: bp@alien8.de
>>Cc: hpa@zytor.com
>>Cc: dave.hansen@linux.intel.com
>>Cc: peterz@infradead.org
>>Cc: boris.ostrovsky@oracle.com
>>Cc: jgross@suse.com
>>Cc: bhe@redhat.com
>>Cc: willy@infradead.org
>>Cc: linux-mm@kvack.org
>>Cc: stable@vger.kernel.org
>>Link: https://lkml.kernel.org/r/20181026122856.66224-2-kirill.shutemov@linux.intel.com
>
>Queued for 4.18, thank you.
... and right after sending this mail I realized that 4.18 is EOL, so
ignore this mail :)
--
Thanks,
Sasha
prev parent reply other threads:[~2018-11-25 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 12:23 FAILED: patch "[PATCH] x86/mm: Move LDT remap out of KASLR region on 5-level paging" failed to apply to 4.18-stable tree gregkh
2018-11-23 11:53 ` Kirill A. Shutemov
2018-11-24 15:53 ` Sasha Levin
2018-11-24 15:57 ` Sasha Levin [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=20181124155752.GV1917@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=luto@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@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