Message ID | 20181119214934.6174-10-yu-cheng.yu@intel.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | Control-flow Enforcement: Branch Tracking, PTRACE | expand |
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> > > Add ENDBR32 to vsyscall entry point. $SUBJECT should be "x86/vdso/32: Add ENDBR32 to __kernel_vsyscall entry point". --Andy
On Mon, 2018-11-19 at 14:23 -0800, Andy Lutomirski wrote: > 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> > > > > Add ENDBR32 to vsyscall entry point. > > $SUBJECT should be "x86/vdso/32: Add ENDBR32 to __kernel_vsyscall entry > point". I will fix it. Yu-cheng
diff --git a/arch/x86/entry/vdso/vdso32/system_call.S b/arch/x86/entry/vdso/vdso32/system_call.S index 263d7433dea8..2fc8141fff4e 100644 --- a/arch/x86/entry/vdso/vdso32/system_call.S +++ b/arch/x86/entry/vdso/vdso32/system_call.S @@ -14,6 +14,9 @@ ALIGN __kernel_vsyscall: CFI_STARTPROC +#ifdef CONFIG_X86_INTEL_BRANCH_TRACKING_USER + endbr32 +#endif /* * Reshuffle regs so that all of any of the entry instructions * will preserve enough state.