From: Baskov Evgeniy <baskov@ispras.ru>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Baskov Evgeniy <baskov@ispras.ru>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-doc@vger.kernel.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RFC 0/5] Handle UEFI NX-restricted page tables
Date: Wed, 10 Nov 2021 13:46:08 +0300 [thread overview]
Message-ID: <20211110104613.23881-1-baskov@ispras.ru> (raw)
Note, that this patch series is RFC, since it is yet untested
and possibly incompatible with AMD SEV and related extensions.
The UEFI specification states that certain memory regions may
not have every permission, i.e. may not be writable or executable.
Furthermore there exist some implementations (at least on i386/x86_64)
that restrict execution of memory regions expected by the kernel to
be executable. E.g. first megabyte of address space, where trampoline
for switching between 4/5 level paging is placed and memory regions,
allocated as loader data.
This patch series allows Linux kernel to boot on such UEFI
implementations on i386 and x86_64.
The simplest way to achieve that on i386 is to disable paging
before jumping to potentially relocated code.
x86_64, on the other hand, does not allow disabling paging so it
is required to build temporary page tables containing memory regions
required for Linux kernel to boot with appropriate access permissions.
Baskov Evgeniy (5):
Docs: document notemppt option
efi: Add option for handling efi memory protection
libstub: build temporary page table without NX-bit
efi/x86_64: set page table if provided by libstub
efi/x86: Disable paging when booting via efistub
Documentation/admin-guide/kernel-parameters.txt | 7
arch/x86/boot/compressed/head_32.S | 12 +
arch/x86/boot/compressed/head_64.S | 12 +
drivers/firmware/efi/Kconfig | 17 ++
drivers/firmware/efi/libstub/Makefile | 2
drivers/firmware/efi/libstub/efi-stub-helper.c | 3
drivers/firmware/efi/libstub/efistub.h | 10 +
drivers/firmware/efi/libstub/temp-pgtable.c | 190 ++++++++++++++++++++++++
drivers/firmware/efi/libstub/x86-stub.c | 8 -
9 files changed, 258 insertions(+), 3 deletions(-)
next reply other threads:[~2021-11-10 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 10:46 Baskov Evgeniy [this message]
2021-11-10 10:46 ` [PATCH RFC 1/5] efi/x86: Disable paging when booting via efistub Baskov Evgeniy
2021-11-10 10:46 ` [PATCH RFC 2/5] efi/x86_64: set page table if provided by libstub Baskov Evgeniy
2021-11-10 10:46 ` [PATCH RFC 3/5] libstub: build temporary page table without NX-bit Baskov Evgeniy
2021-11-10 10:46 ` [PATCH RFC 4/5] efi: Add option for handling efi memory protection Baskov Evgeniy
2021-11-10 10:46 ` [PATCH RFC 5/5] Docs: document notemppt option Baskov Evgeniy
2021-11-10 11:11 ` [PATCH RFC 0/5] Handle UEFI NX-restricted page tables Ard Biesheuvel
2021-11-25 7:36 ` baskov
2021-12-16 17:30 ` Ard Biesheuvel
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=20211110104613.23881-1-baskov@ispras.ru \
--to=baskov@ispras.ru \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 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 NNTP newsgroup(s).