From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [PATCH] x86,seccomp,prctl: Remove PR_TSC_SIGSEGV and seccomp TSC filtering Date: Fri, 3 Oct 2014 23:12:04 +0200 Message-ID: <20141003211204.GQ10583@worktop.programming.kicks-ass.net> References: <20141003201409.GM10583@worktop.programming.kicks-ass.net> <20141003204443.GP10583@worktop.programming.kicks-ass.net> <20141003210213.GG6324@worktop.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andy Lutomirski Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Ingo Molnar , Kees Cook , Andrea Arcangeli , Erik Bosman , "H. Peter Anvin" , Linux API , Michael Kerrisk-manpages , Paul Mackerras , Arnaldo Carvalho de Melo , X86 ML List-Id: linux-api@vger.kernel.org On Fri, Oct 03, 2014 at 02:04:53PM -0700, Andy Lutomirski wrote: > On Fri, Oct 3, 2014 at 2:02 PM, Peter Zijlstra wrote: > > Something like so.. slightly less ugly and possibly with more > > complicated conditions setting the cr4 if you want to fix tsc vs seccomp > > as well. > > This will crash anything that tries rdpmc in an allow-everything > seccomp sandbox. It's also not very compatible with my grand scheme > of allowing rdtsc to be turned off without breaking clock_gettime. :) Well, we clear cap_user_rdpmc, so everybody who still tries it gets what he deserves, no problem there. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753324AbaJCVMM (ORCPT ); Fri, 3 Oct 2014 17:12:12 -0400 Received: from casper.infradead.org ([85.118.1.10]:36464 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750780AbaJCVMJ (ORCPT ); Fri, 3 Oct 2014 17:12:09 -0400 Date: Fri, 3 Oct 2014 23:12:04 +0200 From: Peter Zijlstra To: Andy Lutomirski Cc: "linux-kernel@vger.kernel.org" , Ingo Molnar , Kees Cook , Andrea Arcangeli , Erik Bosman , "H. Peter Anvin" , Linux API , Michael Kerrisk-manpages , Paul Mackerras , Arnaldo Carvalho de Melo , X86 ML Subject: Re: [PATCH] x86,seccomp,prctl: Remove PR_TSC_SIGSEGV and seccomp TSC filtering Message-ID: <20141003211204.GQ10583@worktop.programming.kicks-ass.net> References: <20141003201409.GM10583@worktop.programming.kicks-ass.net> <20141003204443.GP10583@worktop.programming.kicks-ass.net> <20141003210213.GG6324@worktop.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 03, 2014 at 02:04:53PM -0700, Andy Lutomirski wrote: > On Fri, Oct 3, 2014 at 2:02 PM, Peter Zijlstra wrote: > > Something like so.. slightly less ugly and possibly with more > > complicated conditions setting the cr4 if you want to fix tsc vs seccomp > > as well. > > This will crash anything that tries rdpmc in an allow-everything > seccomp sandbox. It's also not very compatible with my grand scheme > of allowing rdtsc to be turned off without breaking clock_gettime. :) Well, we clear cap_user_rdpmc, so everybody who still tries it gets what he deserves, no problem there.