Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754603AbaF1ATr (ORCPT ); Fri, 27 Jun 2014 20:19:47 -0400 Received: from mail-la0-f49.google.com ([209.85.215.49]:62432 "EHLO mail-la0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754302AbaF1ATq (ORCPT ); Fri, 27 Jun 2014 20:19:46 -0400 MIME-Version: 1.0 In-Reply-To: <1403913966-4927-8-git-send-email-ast@plumgrid.com> References: <1403913966-4927-1-git-send-email-ast@plumgrid.com> <1403913966-4927-8-git-send-email-ast@plumgrid.com> From: Andy Lutomirski Date: Fri, 27 Jun 2014 17:19:24 -0700 Message-ID: Subject: Re: [PATCH RFC net-next 07/14] bpf: expand BPF syscall with program load/unload To: Alexei Starovoitov Cc: "David S. Miller" , Ingo Molnar , Linus Torvalds , Steven Rostedt , Daniel Borkmann , Chema Gonzalez , Eric Dumazet , Peter Zijlstra , Arnaldo Carvalho de Melo , Jiri Olsa , Thomas Gleixner , "H. Peter Anvin" , Andrew Morton , Kees Cook , Linux API , Network Development , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 27, 2014 at 5:05 PM, Alexei Starovoitov wrote: > eBPF programs are safe run-to-completion functions with load/unload > methods from userspace similar to kernel modules. > > User space API: > > - load eBPF program > prog_id = bpf_prog_load(int prog_id, bpf_prog_type, struct nlattr *prog, int len) > > where 'prog' is a sequence of sections (currently TEXT and LICENSE) > TEXT - array of eBPF instructions > LICENSE - GPL compatible > + > + err = -EINVAL; > + /* look for mandatory license string */ > + if (!tb[BPF_PROG_LICENSE]) > + goto free_attr; > + > + /* eBPF programs must be GPL compatible */ > + if (!license_is_gpl_compatible(nla_data(tb[BPF_PROG_LICENSE]))) > + goto free_attr; Seriously? My mind boggles. --Andy -- 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/