[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190729145128.GB21120@linux.intel.com>
Date: Mon, 29 Jul 2019 07:51:29 -0700
From: Sean Christopherson <sean.j.christopherson@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
Andy Lutomirski <luto@...nel.org>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Kees Cook <keescook@...omium.org>,
Paul Bolle <pebolle@...cali.nl>, Will Deacon <will@...nel.org>
Subject: Re: [patch 4/5] x86/vdso/32: Use 32bit syscall fallback
On Sun, Jul 28, 2019 at 03:12:55PM +0200, Thomas Gleixner wrote:
> The generic VDSO implementation uses the Y2038 safe clock_gettime64() and
> clock_getres_time64() syscalls as fallback for 32bit VDSO. This breaks
> seccomp setups because these syscalls might be not (yet) allowed.
>
> Implement the 32bit variants which use the legacy syscalls and select the
> variant in the core library.
>
> The 64bit time variants are not removed because they are required for the
> time64 based vdso accessors.
>
> Reported-by: Sean Christopherson <sean.j.christopherson@...el.com>
> Reported-by: Paul Bolle <pebolle@...cali.nl>
> Suggested-by: Andy Lutomirski <luto@...nel.org>
> Fixes: 7ac870747988 ("x86/vdso: Switch to generic vDSO implementation")
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> ---
Reviewed-and-tested-by: Sean Christopherson <sean.j.christopherson@...el.com>
Powered by blists - more mailing lists