From: Borislav Petkov <bp@alien8.de>
To: Gary R Hook <ghook@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Hook, Gary" <Gary.Hook@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"x86@kernel.org" <x86@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"luto@kernel.org" <luto@kernel.org>,
Alexander Potapenko <glider@google.com>
Subject: Re: [PATCH] x86/mm/mem_encrypt: Disable all instrumentation for SME early boot code
Date: Fri, 26 Apr 2019 18:24:25 +0200 [thread overview]
Message-ID: <20190426162425.GI4608@zn.tnic> (raw)
In-Reply-To: <b0ee2570-c9ba-2a7c-2a8b-0dfa46685e62@amd.com>
On Fri, Apr 26, 2019 at 03:11:17PM +0000, Gary R Hook wrote:
> 2) Turn off instrumentation for lib/cmdline.c. The risk is that any
> changes to its code would not enjoy the benefits of KASAN/etc testing
> (if enabled).
What happened to Thomas' suggestion to turn off instrumentation for
those files only when CONFIG_AMD_MEM_ENCRYPT=y?
Which is a variant of 2) above with ifdeffery.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-04-26 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 20:26 [PATCH] x86/mm/mem_encrypt: Disable all instrumentation for SME early boot code Hook, Gary
2019-04-04 20:42 ` Thomas Gleixner
2019-04-08 16:46 ` Gary R Hook
2019-04-08 16:58 ` Borislav Petkov
2019-04-08 18:41 ` Gary R Hook
2019-04-08 19:08 ` Borislav Petkov
2019-04-09 13:47 ` Lendacky, Thomas
2019-04-26 15:11 ` Gary R Hook
2019-04-26 16:24 ` Borislav Petkov [this message]
2019-04-29 20:16 ` Gary R Hook
2019-04-29 20:51 ` Borislav Petkov
2019-04-29 21:22 ` Gary R Hook
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=20190426162425.GI4608@zn.tnic \
--to=bp@alien8.de \
--cc=Gary.Hook@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=ghook@amd.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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 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.