From: David Miller <davem@davemloft.net>
To: jbacik@fb.com
Cc: kernel-team@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next][v2] bpf: test for AND edge cases
Date: Mon, 06 Feb 2017 22:36:17 -0500 (EST) [thread overview]
Message-ID: <20170206.223617.1798901649248376676.davem@davemloft.net> (raw)
In-Reply-To: <1486157123-11066-1-git-send-email-jbacik@fb.com>
From: Josef Bacik <jbacik@fb.com>
Date: Fri, 3 Feb 2017 16:25:23 -0500
> These two tests are based on the work done for f23cc643f9ba. The first test is
> just a basic one to make sure we don't allow AND'ing negative values, even if it
> would result in a valid index for the array. The second is a cleaned up version
> of the original testcase provided by Jann Horn that resulted in the commit.
>
> Acked-by: Alexei Starovoitov <ast@kernel.org>
> Acked-by: Daniel Borkmann <daniel@iogearbox.net>
> Signed-off-by: Josef Bacik <jbacik@fb.com>
> ---
> v1->v2:
> -rebased onto net-next
Applied.
prev parent reply other threads:[~2017-02-07 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 21:25 [PATCH net-next][v2] bpf: test for AND edge cases Josef Bacik
2017-02-07 3:36 ` David Miller [this message]
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=20170206.223617.1798901649248376676.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.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;
as well as URLs for NNTP newsgroup(s).