[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42cd7cc3-4e44-4be5-7494-584526a55ced@fb.com>
Date: Wed, 23 Aug 2017 07:41:56 -0700
From: Alexei Starovoitov <ast@...com>
To: Edward Cree <ecree@...arflare.com>, <davem@...emloft.net>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Daniel Borkmann <daniel@...earbox.net>
CC: <netdev@...r.kernel.org>,
iovisor-dev <iovisor-dev@...ts.iovisor.org>
Subject: Re: [PATCH v2 net-next 4/5] bpf/verifier: remove
varlen_map_value_access flag
On 8/23/17 7:10 AM, Edward Cree wrote:
> The optimisation it does is broken when the 'new' register value has a
> variable offset and the 'old' was constant. I broke it with my pointer
> types unification (see Fixes tag below), before which the 'new' value
> would have type PTR_TO_MAP_VALUE_ADJ and would thus not compare equal;
> other changes in that patch mean that its original behaviour (ignore
> min/max values) cannot be restored.
> Tests on a sample set of cilium programs show no change in count of
> processed instructions.
>
> Fixes: f1174f77b50c ("bpf/verifier: rework value tracking")
> Signed-off-by: Edward Cree <ecree@...arflare.com>
Acked-by: Alexei Starovoitov <ast@...nel.org>
Powered by blists - more mailing lists