From: Song Liu <song@kernel.org>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf-next 3/3] selftests/bpf: use target-less SEC() definitions in various tests
Date: Fri, 8 Apr 2022 14:08:15 -0700 [thread overview]
Message-ID: <CAPhsuW4oEtV8i9JEx8fLN-Yp54VWdADc=hUYNfWFbrDHVudNww@mail.gmail.com> (raw)
In-Reply-To: <20220408203433.2988727-4-andrii@kernel.org>
On Fri, Apr 8, 2022 at 1:34 PM Andrii Nakryiko <andrii@kernel.org> wrote:
>
> Add new or modify existing SEC() definitions to be target-less and
> validate that libbpf handles such program definitions correctly.
>
> For kprobe/kretprobe we also add explicit test that generic
> bpf_program__attach() works in cases when kprobe definition contains
> proper target. It wasn't previously tested as selftests code always
> explicitly specified the target regardless.
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Song Liu <songliubraving@fb.com>
prev parent reply other threads:[~2022-04-08 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 20:34 [PATCH bpf-next 0/3] Add target-less tracing SEC() definitions Andrii Nakryiko
2022-04-08 20:34 ` [PATCH bpf-next 1/3] libbpf: allow "incomplete" basic " Andrii Nakryiko
2022-04-08 20:46 ` Song Liu
2022-04-08 22:21 ` Andrii Nakryiko
2022-04-08 22:36 ` Song Liu
2022-04-08 20:34 ` [PATCH bpf-next 2/3] libbpf: support target-less SEC() definitions for BTF-backed programs Andrii Nakryiko
2022-04-08 21:08 ` Song Liu
2022-04-08 20:34 ` [PATCH bpf-next 3/3] selftests/bpf: use target-less SEC() definitions in various tests Andrii Nakryiko
2022-04-08 21:08 ` Song Liu [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='CAPhsuW4oEtV8i9JEx8fLN-Yp54VWdADc=hUYNfWFbrDHVudNww@mail.gmail.com' \
--to=song@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
/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.