[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF=yD-KrunO4moO6xj32M=cbv2J6qYjJtEBzopE6QSmNr3SnTw@mail.gmail.com>
Date: Tue, 5 Feb 2019 15:19:52 -0500
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Stanislav Fomichev <sdf@...gle.com>
Cc: Network Development <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
simon.horman@...ronome.com, Willem de Bruijn <willemb@...gle.com>
Subject: Re: [RFC bpf-next 5/7] bpf: when doing BPF_PROG_TEST_RUN for flow
dissector use no-skb mode
On Tue, Feb 5, 2019 at 12:58 PM Stanislav Fomichev <sdf@...gle.com> wrote:
>
> Now that we have __flow_bpf_dissect which works on raw data (by
> constructing temporary on-stack skb), use it when doing
> BPF_PROG_TEST_RUN for flow dissector.
>
> This should help us catch any possible bugs due to missing shinfo on
> the on-stack skb.
>
> Note that existing __skb_flow_bpf_dissect swallows L2 headers and returns
> nhoff=0, we need to preserve the existing behavior.
>
> Signed-off-by: Stanislav Fomichev <sdf@...gle.com>
> ---
> net/bpf/test_run.c | 52 +++++++++++++++-------------------------------
> 1 file changed, 17 insertions(+), 35 deletions(-)
>
> ret = bpf_test_finish(kattr, uattr, &flow_keys, sizeof(flow_keys),
> retval, duration);
> -
> - kfree_skb(skb);
> - kfree(sk);
> + kfree(data);
> return ret;
> +
nit: unnecessary whitespace line
> }
Powered by blists - more mailing lists