From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Edward Cree <ecree@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH net] bpf/verifier: reject BPF_ALU64|BPF_END
Date: Fri, 15 Sep 2017 08:50:46 -0700 [thread overview]
Message-ID: <20170915155044.e3jbkdbdbkaq7zun@ast-mbp> (raw)
In-Reply-To: <8c3d5513-6171-3e68-56df-1efd0e87f071@solarflare.com>
On Fri, Sep 15, 2017 at 02:37:38PM +0100, Edward Cree wrote:
> Neither ___bpf_prog_run nor the JITs accept it.
> Also adds a new test case.
>
> Fixes: 17a5267067f3 ("bpf: verifier (add verifier core)")
> Signed-off-by: Edward Cree <ecree@solarflare.com>
Good catch. Thanks!
Acked-by: Alexei Starovoitov <ast@kernel.org>
next prev parent reply other threads:[~2017-09-15 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 13:37 [PATCH net] bpf/verifier: reject BPF_ALU64|BPF_END Edward Cree
2017-09-15 15:50 ` Alexei Starovoitov [this message]
2017-09-15 18:01 ` Daniel Borkmann
2017-09-15 22:02 ` David Miller
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=20170915155044.e3jbkdbdbkaq7zun@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox