From: Daniel Borkmann <daniel@iogearbox.net>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: "Jiří Pírko" <jiri@resnulli.us>,
"Network Development" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 3/7] ebpf: check first for MAXINSNS in bpf_prog_load
Date: Thu, 12 Feb 2015 21:43:55 +0100 [thread overview]
Message-ID: <54DD108B.60401@iogearbox.net> (raw)
In-Reply-To: <CAMEtUuxatiqWCGeNmKEXHRFR=68L9=SnpYrnzQm-+WnRzGvtzg@mail.gmail.com>
On 02/11/2015 02:21 AM, Alexei Starovoitov wrote:
...
> So if user specified 'my_ultra_long_proprietery_license'
> that should be fine. The program should still be accepted
> and marked as non-gpl.
Yep, true. Most likely I'll drop this one for non-RFC anyway
as it's not much of value. ;)
next prev parent reply other threads:[~2015-02-12 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 0:15 [RFC PATCH net-next 0/7] eBPF support for cls_bpf Daniel Borkmann
2015-02-11 0:15 ` [PATCH net-next 1/7] ebpf: remove kernel test stubs Daniel Borkmann
2015-02-11 0:42 ` Alexei Starovoitov
2015-02-11 0:15 ` [PATCH net-next 2/7] ebpf: constify various function pointer structs Daniel Borkmann
2015-02-11 0:43 ` Alexei Starovoitov
2015-02-11 0:15 ` [PATCH net-next 3/7] ebpf: check first for MAXINSNS in bpf_prog_load Daniel Borkmann
2015-02-11 1:21 ` Alexei Starovoitov
2015-02-12 20:43 ` Daniel Borkmann [this message]
2015-02-11 0:15 ` [PATCH net-next 4/7] ebpf: extend program type/subsystem registration Daniel Borkmann
2015-02-11 0:15 ` [PATCH net-next 5/7] ebpf: export BPF_PSEUDO_MAP_FD to uapi Daniel Borkmann
2015-02-11 1:39 ` Alexei Starovoitov
2015-02-11 0:15 ` [PATCH net-next 6/7] ebpf: remove CONFIG_BPF_SYSCALL ifdefs in socket filter code Daniel Borkmann
2015-02-11 0:15 ` [PATCH net-next 7/7] cls_bpf: add initial eBPF support for programmable classifiers Daniel Borkmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DD108B.60401@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.