From: Tom Lendacky <thomas.lendacky@amd.com>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Young <dyoung@redhat.com>,
Brijesh Singh <brijesh.singh@amd.com>,
<kexec@lists.infradead.org>
Subject: [PATCH v1 0/2] x86: Secure Memory Encryption (SME) fixes 2017-07-26
Date: Wed, 26 Jul 2017 13:04:32 -0500 [thread overview]
Message-ID: <cover.1501092102.git.thomas.lendacky@amd.com> (raw)
This patch series addresses some issues found during further testing of
Secure Memory Encryption (SME).
The following fixes are included in this update series:
- Fix a cache-related memory corruption when kexec is invoked in
successive instances
- Remove the encryption mask from the protection properties returned
by arch_apei_get_mem_attribute() when SME is active
---
This patch series is based off of the master branch of tip:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
Commit 8333bcad393c ("Merge branch 'x86/asm'")
Cc: <kexec@lists.infradead.org>
Tom Lendacky (2):
x86/mm, kexec: Fix memory corruption with SME on successive kexecs
acpi, x86: Remove encryption mask from ACPI page protection type
arch/x86/include/asm/acpi.h | 7 ++++++-
arch/x86/kernel/relocate_kernel_64.S | 7 +++++++
2 files changed, 13 insertions(+), 1 deletion(-)
--
1.9.1
next reply other threads:[~2017-07-26 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 18:04 Tom Lendacky [this message]
2017-07-26 18:04 ` [PATCH v1 1/2] x86/mm, kexec: Fix memory corruption with SME on successive kexecs Tom Lendacky
2017-07-27 7:17 ` Ingo Molnar
2017-07-27 14:15 ` Tom Lendacky
2017-07-27 17:34 ` Linus Torvalds
2017-07-27 18:47 ` Tom Lendacky
2017-07-26 18:04 ` [PATCH v1 2/2] acpi, x86: Remove encryption mask from ACPI page protection type Tom Lendacky
2017-07-27 7:39 ` Ingo Molnar
2017-07-27 14:53 ` Tom Lendacky
2017-07-27 14:41 ` Borislav Petkov
2017-07-27 14:57 ` Tom Lendacky
2017-07-28 6:28 ` Ingo Molnar
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.1501092102.git.thomas.lendacky@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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).