From: Andy Lutomirski <luto@amacapital.net>
To: Yu-cheng Yu <yu-cheng.yu@intel.com>
Cc: X86 ML <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
linux-arch <linux-arch@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Balbir Singh <bsingharora@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Eugene Syromiatnikov <esyr@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
"H. J. Lu" <hjl.tools@gmail.com>, Jann Horn <jannh@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Kees Cook <keescook@chromium.org>,
Mike Kravetz <mike.kravetz@oracle.com>, Nadav Amit <nadav.am>
Subject: Re: [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO
Date: Mon, 19 Nov 2018 14:17:48 -0800 [thread overview]
Message-ID: <CALCETrW9ABDotyM020V147+kuizpTRJUAANn-6kUt6-h0Qn0og@mail.gmail.com> (raw)
In-Reply-To: <20181119214934.6174-9-yu-cheng.yu@intel.com>
On Mon, Nov 19, 2018 at 1:55 PM Yu-cheng Yu <yu-cheng.yu@intel.com> wrote:
>
> From: "H.J. Lu" <hjl.tools@gmail.com>
>
> When Intel indirect branch tracking is enabled, functions in vDSO which
> may be called indirectly must have endbr32 or endbr64 as the first
> instruction. Compiler must support -fcf-protection=branch so that it
> can be used to compile vDSO.
>
> Signed-off-by: H.J. Lu <hjl.tools@gmail.com>
> ---
> arch/x86/entry/vdso/.gitignore | 4 ++++
> arch/x86/entry/vdso/Makefile | 12 +++++++++++-
> arch/x86/entry/vdso/vdso-layout.lds.S | 1 +
> 3 files changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/entry/vdso/.gitignore b/arch/x86/entry/vdso/.gitignore
> index aae8ffdd5880..552941fdfae0 100644
> --- a/arch/x86/entry/vdso/.gitignore
> +++ b/arch/x86/entry/vdso/.gitignore
> @@ -5,3 +5,7 @@ vdso32-sysenter-syms.lds
> vdso32-int80-syms.lds
> vdso-image-*.c
> vdso2c
> +vclock_gettime.S
> +vgetcpu.S
> +vclock_gettime.asm
> +vgetcpu.asm
What's this hunk about?
next prev parent reply other threads:[~2018-11-19 22:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 21:49 [RFC PATCH v6 00/11] Control-flow Enforcement: Branch Tracking, PTRACE Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 01/11] x86/cet/ibt: Add Kconfig option for user-mode Indirect Branch Tracking Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 02/11] x86/cet/ibt: User-mode indirect branch tracking support Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 03/11] x86/cet/ibt: Add IBT legacy code bitmap setup function Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 04/11] mm/mmap: Add IBT bitmap size to address space limit check Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 05/11] x86/cet/ibt: ELF header parsing for IBT Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 06/11] x86/cet/ibt: Add arch_prctl functions " Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 07/11] x86/cet/ibt: Add ENDBR to op-code-map Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 08/11] x86: Insert endbr32/endbr64 to vDSO Yu-cheng Yu
2018-11-19 22:17 ` Andy Lutomirski [this message]
2018-11-19 22:43 ` Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 09/11] x86/vsyscall/32: Add ENDBR32 to vsyscall entry point Yu-cheng Yu
2018-11-19 22:23 ` Andy Lutomirski
2018-11-19 22:40 ` Yu-cheng Yu
2018-11-19 21:49 ` [RFC PATCH v6 10/11] x86/vsyscall/64: Add ENDBR64 to vsyscall entry points Yu-cheng Yu
2018-11-19 22:22 ` Andy Lutomirski
2018-11-19 21:49 ` [RFC PATCH v6 11/11] x86/cet: Add PTRACE interface for CET Yu-cheng Yu
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=CALCETrW9ABDotyM020V147+kuizpTRJUAANn-6kUt6-h0Qn0og@mail.gmail.com \
--to=luto@amacapital.net \
--cc=arnd@arndb.de \
--cc=bsingharora@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=esyr@redhat.com \
--cc=fweimer@redhat.com \
--cc=gorcunov@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/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).