netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: William Tu <u9012063@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	ast@kernel.org, Gianluca Borello <g.borello@gmail.com>
Subject: Re: [PATCH net-next 5/5] bpf: enable verifier to better track const alu ops
Date: Wed, 25 Jan 2017 21:19:09 +0100	[thread overview]
Message-ID: <5889083D.7000702@iogearbox.net> (raw)
In-Reply-To: <CALDO+Sa5w3munbMVBYGAu1mpXE0Bj9kV_E=DvPq0YtunVnQf1Q@mail.gmail.com>

On 01/25/2017 04:56 PM, William Tu wrote:
> Looks good to me, I tested with several complex program without any
> problem. Thanks for the patch.

Thanks for re-testing, William!

  reply	other threads:[~2017-01-25 20:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24  0:06 [PATCH net-next 0/5] Misc BPF improvements Daniel Borkmann
2017-01-24  0:06 ` [PATCH net-next 1/5] bpf: simplify __is_valid_access test on cb Daniel Borkmann
2017-01-24  0:06 ` [PATCH net-next 2/5] bpf: enable load bytes helper for filter/reuseport progs Daniel Borkmann
2017-01-24  0:06 ` [PATCH net-next 3/5] bpf: allow option for setting bpf_l4_csum_replace from scratch Daniel Borkmann
2017-01-24  0:06 ` [PATCH net-next 4/5] bpf: add prog tag test case to bpf selftests Daniel Borkmann
2017-01-24  0:06 ` [PATCH net-next 5/5] bpf: enable verifier to better track const alu ops Daniel Borkmann
2017-01-25 15:56   ` William Tu
2017-01-25 20:19     ` Daniel Borkmann [this message]
2017-01-24 19:49 ` [PATCH net-next 0/5] Misc BPF improvements 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=5889083D.7000702@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.net \
    --cc=g.borello@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=u9012063@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).