From: Edward Cree <ecree@solarflare.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: <davem@davemloft.net>, Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
iovisor-dev <iovisor-dev@lists.iovisor.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 3/5] bpf/verifier: feed pointer-to-unknown-scalar casts into scalar ALU path
Date: Thu, 8 Jun 2017 16:25:39 +0100 [thread overview]
Message-ID: <2363ab5f-c344-900b-78ee-41e2eb0dd40f@solarflare.com> (raw)
In-Reply-To: <20170608023540.5ecmmobhl2rtgrg5@ast-mbp>
On 08/06/17 03:35, Alexei Starovoitov wrote:
> such large back and forth move doesn't help reviewing.
> may be just merge it into previous patch?
> Or keep that function in the right place in patch 2 already?
I think 'diff' got a bit confused, and maybe with different options I could
have got it to produce something more readable. But I think I will just
merge this into patch 2; it's only separate because it started out as an
experiment.
-Ed
next prev parent reply other threads:[~2017-06-08 15:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 14:55 [RFC PATCH net-next 0/5] bpf: rewrite value tracking in verifier Edward Cree
2017-06-07 14:58 ` [RFC PATCH net-next 1/5] selftests/bpf: add test for mixed signed and unsigned bounds checks Edward Cree
2017-06-07 14:58 ` [RFC PATCH net-next 2/5] bpf/verifier: rework value tracking Edward Cree
2017-06-08 2:32 ` Alexei Starovoitov
2017-06-08 14:53 ` Edward Cree
2017-06-08 16:45 ` Alexei Starovoitov
2017-06-08 19:38 ` Edward Cree
2017-06-08 21:20 ` Alexei Starovoitov
2017-06-09 13:25 ` Daniel Borkmann
2017-06-07 14:58 ` [RFC PATCH net-next 3/5] bpf/verifier: feed pointer-to-unknown-scalar casts into scalar ALU path Edward Cree
2017-06-08 2:35 ` Alexei Starovoitov
2017-06-08 15:25 ` Edward Cree [this message]
2017-06-08 16:50 ` Alexei Starovoitov
2017-06-08 17:12 ` Edward Cree
2017-06-08 18:41 ` Alexei Starovoitov
2017-06-08 19:07 ` Edward Cree
2017-06-08 21:17 ` Alexei Starovoitov
2017-06-07 14:59 ` [RFC PATCH net-next 4/5] bpf/verifier: track signed and unsigned min/max values Edward Cree
2017-06-08 2:40 ` Alexei Starovoitov
2017-06-08 15:23 ` Edward Cree
2017-06-08 16:47 ` Alexei Starovoitov
2017-06-07 15:00 ` [RFC PATCH net-next 5/5] selftests/bpf: change test_verifier expectations Edward Cree
2017-06-08 2:43 ` Alexei Starovoitov
2017-06-08 15:27 ` Edward Cree
2017-06-08 20:18 ` [RFC PATCH net-next 0/5] bpf: rewrite value tracking in verifier 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=2363ab5f-c344-900b-78ee-41e2eb0dd40f@solarflare.com \
--to=ecree@solarflare.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=iovisor-dev@lists.iovisor.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®