From: Daniel Borkmann <daniel@iogearbox.net>
To: Dmitry Yakunin <zeil@yandex-team.ru>,
alexei.starovoitov@gmail.com, netdev@vger.kernel.org,
bpf@vger.kernel.org
Cc: eric.dumazet@gmail.com, sdf@google.com
Subject: Re: [PATCH bpf-next v6 0/2] bpf: cgroup skb improvements for bpf_prog_test_run
Date: Mon, 3 Aug 2020 23:55:33 +0200 [thread overview]
Message-ID: <a980acba-03cf-b3c3-7f49-20740bcdeb08@iogearbox.net> (raw)
In-Reply-To: <20200803090545.82046-1-zeil@yandex-team.ru>
On 8/3/20 11:05 AM, Dmitry Yakunin wrote:
> This patchset contains some improvements for testing cgroup/skb programs
> through BPF_PROG_TEST_RUN command.
>
> v2:
> - fix build without CONFIG_CGROUP_BPF (kernel test robot <lkp@intel.com>)
>
> v3:
> - fix build without CONFIG_IPV6 (kernel test robot <lkp@intel.com>)
>
> v4:
> - remove cgroup storage related commits for future rework (Daniel Borkmann)
>
> v5:
> - check skb length before access to inet headers (Eric Dumazet)
>
> v6:
> - do not use pskb_may_pull() in skb length checking (Alexei Starovoitov)
>
> Dmitry Yakunin (2):
> bpf: setup socket family and addresses in bpf_prog_test_run_skb
> bpf: allow to specify ifindex for skb in bpf_prog_test_run_skb
>
> net/bpf/test_run.c | 39 ++++++++++++++++++++++--
> tools/testing/selftests/bpf/prog_tests/skb_ctx.c | 5 +++
> 2 files changed, 42 insertions(+), 2 deletions(-)
>
Looks good, applied, thanks!
prev parent reply other threads:[~2020-08-03 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 9:05 [PATCH bpf-next v6 0/2] bpf: cgroup skb improvements for bpf_prog_test_run Dmitry Yakunin
2020-08-03 9:05 ` [PATCH bpf-next v6 1/2] bpf: setup socket family and addresses in bpf_prog_test_run_skb Dmitry Yakunin
2020-08-03 9:05 ` [PATCH bpf-next v6 2/2] bpf: allow to specify ifindex for skb " Dmitry Yakunin
2020-08-03 21:55 ` Daniel Borkmann [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=a980acba-03cf-b3c3-7f49-20740bcdeb08@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=zeil@yandex-team.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.