Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752824Ab2BVUBO (ORCPT ); Wed, 22 Feb 2012 15:01:14 -0500 Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]:47252 "EHLO mail-lpp01m010-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751871Ab2BVUBM convert rfc822-to-8bit (ORCPT ); Wed, 22 Feb 2012 15:01:12 -0500 MIME-Version: 1.0 In-Reply-To: <4F4547C6.8050001@zytor.com> References: <1329845435-2313-1-git-send-email-wad@chromium.org> <1329845435-2313-5-git-send-email-wad@chromium.org> <38d58caa17befe422065efe5dc451a34.squirrel@webmail.greenhost.nl> <4F4547C6.8050001@zytor.com> Date: Wed, 22 Feb 2012 14:01:09 -0600 Message-ID: Subject: Re: [PATCH v10 05/11] seccomp: add system call filtering using BPF From: Will Drewry To: "H. Peter Anvin" Cc: Indan Zupancic , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-doc@vger.kernel.org, kernel-hardening@lists.openwall.com, netdev@vger.kernel.org, x86@kernel.org, arnd@arndb.de, davem@davemloft.net, mingo@redhat.com, oleg@redhat.com, peterz@infradead.org, rdunlap@xenotime.net, mcgrathr@chromium.org, tglx@linutronix.de, luto@mit.edu, eparis@redhat.com, serge.hallyn@canonical.com, djm@mindrot.org, scarybeasts@gmail.com, pmoore@redhat.com, akpm@linux-foundation.org, corbet@lwn.net, eric.dumazet@gmail.com, markus@chromium.org, keescook@chromium.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1853 Lines: 44 On Wed, Feb 22, 2012 at 1:53 PM, H. Peter Anvin wrote: > On 02/22/2012 11:47 AM, Will Drewry wrote: >>> >>> I highly disagree with every filter having to check the mode: Filters that >>> don't check the arch on e.g. x86 are buggy, so they have to check it, even >>> if it's a 32-bit or 64-bit only system, the filters can't know that and >>> needs to check the arch at every syscall entry. All other info in the data >>> depends on the arch, because of this there isn't much code to share between >>> the two archs, so you can as well have one filter for each arch. >>> >>> Alternative approach: Tell the arch at filter install time and only run the >>> filters with the same arch as the current system call. If no filters are run, >>> deny the systemcall. >> >> This was roughly how I first implemented compat and non-compat >> support. ?It causes some implicit behavior across inheritance that is >> not nice though. >> > > This is trivially doable at the BPF level, right? ?Just make this the > first instruction in the program (either deny or jump to a separate > program branch)... and then there is still "one program" without any > weird inheritance issues? Exactly, and that's what the patch does now (after your feedback :) ld arch je arch, 1, 0 ret SECCOMP_RET_KILL At this point, I don't think it makes sense to do it a different way than just in the BPF program even if it does mean leaving out the check could leave the program open to compat-style bugs. At least a shared library and/or good practices should be able to catch that error. thanks! will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/