From: Alexei Starovoitov <ast@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alexei Starovoitov <ast@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
"x86@kernel.org" <x86@kernel.org>,
Networking <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 10/10] selftests/bpf: add kfree_skb raw_tp test
Date: Wed, 9 Oct 2019 17:37:50 +0000 [thread overview]
Message-ID: <c744b787-1f46-fc2e-d921-e2c356a9f849@fb.com> (raw)
In-Reply-To: <CAEf4BzZS3kvunYnPu6x674H08DZKnuc37c9+m4p_2EjdNuDGSg@mail.gmail.com>
On 10/8/19 10:36 PM, Andrii Nakryiko wrote:
> On Fri, Oct 4, 2019 at 10:04 PM Alexei Starovoitov <ast@kernel.org> wrote:
>>
>> Load basic cls_bpf program.
>> Load raw_tracepoint program and attach to kfree_skb raw tracepoint.
>> Trigger cls_bpf via prog_test_run.
>> At the end of test_run kernel will call kfree_skb
>> which will trigger trace_kfree_skb tracepoint.
>> Which will call our raw_tracepoint program.
>> Which will take that skb and will dump it into perf ring buffer.
>> Check that user space received correct packet.
>>
>> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
>> ---
>
> LGTM, few minor nits below.
>
> Acked-by: Andrii Nakryiko <andriin@fb.com>
>
>
>> .../selftests/bpf/prog_tests/kfree_skb.c | 90 +++++++++++++++++++
>> tools/testing/selftests/bpf/progs/kfree_skb.c | 76 ++++++++++++++++
>> 2 files changed, 166 insertions(+)
>> create mode 100644 tools/testing/selftests/bpf/prog_tests/kfree_skb.c
>> create mode 100644 tools/testing/selftests/bpf/progs/kfree_skb.c
>>
>> diff --git a/tools/testing/selftests/bpf/prog_tests/kfree_skb.c b/tools/testing/selftests/bpf/prog_tests/kfree_skb.c
>> new file mode 100644
>> index 000000000000..238bc7024b36
>> --- /dev/null
>> +++ b/tools/testing/selftests/bpf/prog_tests/kfree_skb.c
>> @@ -0,0 +1,90 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +#include <test_progs.h>
>> +
>> +static void on_sample(void *ctx, int cpu, void *data, __u32 size)
>> +{
>> + int ifindex = *(int *)data, duration = 0;
>> + struct ipv6_packet * pkt_v6 = data + 4;
>> +
>> + if (ifindex != 1)
>> + /* spurious kfree_skb not on loopback device */
>> + return;
>> + if (CHECK(size != 76, "check_size", "size %d != 76\n", size))
>
> compiler doesn't complain about %d and size being unsigned?
compile didn't complain. but I fixed it.
>> +SEC("raw_tracepoint/kfree_skb")
>> +int trace_kfree_skb(struct trace_kfree_skb* ctx)
>> +{
>> + struct sk_buff *skb = ctx->skb;
>> + struct net_device *dev;
>> + int ifindex;
>> + struct callback_head *ptr;
>> + void *func;
>
> nit: style checker should have complained about missing empty line
good point. Fixed checkpatch errors.
prev parent reply other threads:[~2019-10-09 17:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 5:03 [PATCH bpf-next 00/10] bpf: revolutionize bpf tracing Alexei Starovoitov
2019-10-05 5:03 ` [PATCH bpf-next 01/10] bpf: add typecast to raw_tracepoints to help BTF generation Alexei Starovoitov
2019-10-05 18:40 ` Andrii Nakryiko
2019-10-06 3:58 ` John Fastabend
2019-10-05 5:03 ` [PATCH bpf-next 02/10] bpf: add typecast to bpf helpers " Alexei Starovoitov
2019-10-05 18:41 ` Andrii Nakryiko
2019-10-06 4:00 ` John Fastabend
2019-10-05 5:03 ` [PATCH bpf-next 03/10] bpf: process in-kernel BTF Alexei Starovoitov
2019-10-06 6:36 ` Andrii Nakryiko
2019-10-06 23:49 ` Alexei Starovoitov
2019-10-07 0:20 ` Andrii Nakryiko
2019-10-09 20:51 ` Martin Lau
2019-10-10 3:43 ` Alexei Starovoitov
2019-10-05 5:03 ` [PATCH bpf-next 04/10] libbpf: auto-detect btf_id of raw_tracepoint Alexei Starovoitov
2019-10-07 23:41 ` Andrii Nakryiko
2019-10-09 2:26 ` Alexei Starovoitov
2019-10-05 5:03 ` [PATCH bpf-next 05/10] bpf: implement accurate raw_tp context access via BTF Alexei Starovoitov
2019-10-07 16:32 ` Alan Maguire
2019-10-09 3:59 ` Alexei Starovoitov
2019-10-08 0:35 ` Andrii Nakryiko
2019-10-09 3:30 ` Alexei Starovoitov
2019-10-09 4:01 ` Andrii Nakryiko
2019-10-09 5:10 ` Andrii Nakryiko
2019-10-10 3:54 ` Alexei Starovoitov
2019-10-05 5:03 ` [PATCH bpf-next 06/10] bpf: add support for BTF pointers to interpreter Alexei Starovoitov
2019-10-08 3:08 ` Andrii Nakryiko
2019-10-05 5:03 ` [PATCH bpf-next 07/10] bpf: add support for BTF pointers to x86 JIT Alexei Starovoitov
2019-10-05 6:03 ` Eric Dumazet
2019-10-09 17:38 ` Andrii Nakryiko
2019-10-09 17:46 ` Alexei Starovoitov
2019-10-05 5:03 ` [PATCH bpf-next 08/10] bpf: check types of arguments passed into helpers Alexei Starovoitov
2019-10-09 18:01 ` Andrii Nakryiko
2019-10-09 19:58 ` Alexei Starovoitov
2019-10-05 5:03 ` [PATCH bpf-next 09/10] bpf: disallow bpf_probe_read[_str] helpers Alexei Starovoitov
2019-10-09 5:29 ` Andrii Nakryiko
2019-10-09 19:38 ` Alexei Starovoitov
2019-10-05 5:03 ` [PATCH bpf-next 10/10] selftests/bpf: add kfree_skb raw_tp test Alexei Starovoitov
2019-10-09 5:36 ` Andrii Nakryiko
2019-10-09 17:37 ` Alexei Starovoitov [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=c744b787-1f46-fc2e-d921-e2c356a9f849@fb.com \
--to=ast@fb.com \
--cc=Kernel-team@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=x86@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).