Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966392AbbD2QwY (ORCPT ); Wed, 29 Apr 2015 12:52:24 -0400 Received: from mail-ie0-f180.google.com ([209.85.223.180]:35498 "EHLO mail-ie0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966257AbbD2QwV (ORCPT ); Wed, 29 Apr 2015 12:52:21 -0400 Date: Wed, 29 Apr 2015 09:46:14 -0700 From: Alexei Starovoitov To: Nicolas Schichan Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Russell King , "David S. Miller" , Daniel Borkmann , Andy Lutomirski , Will Drewry , Kees Cook , netdev@vger.kernel.org Subject: Re: [PATCH 0/4] Seccomp filter JIT support on ARM. Message-ID: <20150429164607.GA12410@Alexeis-MBP.westell.com> References: <1430314657-2552-1-git-send-email-nschichan@freebox.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1430314657-2552-1-git-send-email-nschichan@freebox.fr> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1339 Lines: 36 On Wed, Apr 29, 2015 at 03:37:33PM +0200, Nicolas Schichan wrote: > Greetings, > > The following patches allow the use of the existing JIT code under > arch/arm for seccomp filters. > > The first patch makes bpf_migrate_filter() available so that seccomp > code can use it. > > The second patch invokes the classic BPF JIT code and if this fails > reverts to the internal BPF. The open coded double call to > bpf_convert_filter() and bpf_prog_select_runtime() is replaced by > bpf_migrate_filter() > > The third patch adds support for loads from the seccomp_data structure in > the ARM BPF JIT code. the patches 1,2,3 look fine. > The fourth and final patch fixes a bug in the emit_udiv() function > when used to convert a BPF_ALU | BPF_DIV | BPF_K instruction in the > ARM BPF JIT code. this one looks independent from first three and probably should be sent to stable? Your cc list is different for every patch, why? What tree are you thinking to go through? 1st patch is trivial, but 2nd belongs in seccomp, 3rd and 4th are in arm32... I'd would say arm tree if Kees is ok with it. -- 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/