From: Andy Lutomirski <luto@kernel.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Dave Hansen <dave.hansen@intel.com>, X86 ML <x86@kernel.org>,
Borislav Petkov <bp@alien8.de>
Cc: Neil Berrington <neil.berrington@datacore.com>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH v2 0/2] x86/mm/64: vmalloc pgd synchronization cleanups/fixes
Date: Thu, 25 Jan 2018 13:12:13 -0800 [thread overview]
Message-ID: <cover.1516914529.git.luto@kernel.org> (raw)
Hi all-
Patch 1 is a regression fix and should go to linus and -stable. (Not
necessarily x86/pti. It's needed in 4.14, but if anyone backports
real PTI earlier than 4.14, this patch will *not* be needed. The
regression doesn't really have anything to do with PTI.)
Patch 2 should probably go to normal -tip or even just wait for
Konstantin's ack.
Andy Lutomirski (2):
x86/mm/64: Fix vmapped stack syncing on very-large-memory 4-level
systems
x86/mm/64: Tighten up vmalloc_fault() sanity checks on 5-level kernels
arch/x86/mm/fault.c | 22 +++++++++-------------
arch/x86/mm/tlb.c | 34 +++++++++++++++++++++++++++++-----
2 files changed, 38 insertions(+), 18 deletions(-)
--
2.14.3
next reply other threads:[~2018-01-25 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 21:12 Andy Lutomirski [this message]
2018-01-25 21:12 ` [PATCH v2 1/2] x86/mm/64: Fix vmapped stack syncing on very-large-memory 4-level systems Andy Lutomirski
2018-01-25 21:49 ` Dave Hansen
2018-01-25 22:00 ` Andy Lutomirski
2018-01-26 9:30 ` Ingo Molnar
2018-01-26 18:54 ` Kirill A. Shutemov
2018-01-26 15:06 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2018-01-26 18:51 ` [PATCH v2 1/2] " Kirill A. Shutemov
2018-01-26 19:02 ` Andy Lutomirski
2018-01-26 20:50 ` Kirill A. Shutemov
2018-01-25 21:12 ` [PATCH v2 2/2] x86/mm/64: Tighten up vmalloc_fault() sanity checks on 5-level kernels Andy Lutomirski
2018-01-26 15:07 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
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=cover.1516914529.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.berrington@datacore.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.