From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: KP Singh <kpsingh@kernel.org>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Florent Revest <revest@chromium.org>,
Brendan Jackman <jackmanb@chromium.org>
Subject: Re: [PATCH bpf-next 2/2] bpf/selftests: Update the IMA test to use BPF ring buffer
Date: Wed, 3 Feb 2021 20:59:25 -0800 [thread overview]
Message-ID: <CAEf4Bzb4LzUPkA0SB3W2iri42=4Pv3CveWb+-a6rAJU772HvQA@mail.gmail.com> (raw)
In-Reply-To: <20210203232331.2567162-3-kpsingh@kernel.org>
On Wed, Feb 3, 2021 at 3:23 PM KP Singh <kpsingh@kernel.org> wrote:
>
> Instead of using shared global variables between userspace and BPF, use
> the ring buffer to send the IMA hash on the BPF ring buffer. This helps
> in validating both IMA and the usage of the ringbuffer in sleepable
> programs.
>
> Signed-off-by: KP Singh <kpsingh@kernel.org>
> ---
> .../selftests/bpf/prog_tests/test_ima.c | 23 ++++++++++---
> tools/testing/selftests/bpf/progs/ima.c | 33 ++++++++++++++-----
> 2 files changed, 43 insertions(+), 13 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/test_ima.c b/tools/testing/selftests/bpf/prog_tests/test_ima.c
> index 61fca681d524..23fb4c9e80d1 100644
> --- a/tools/testing/selftests/bpf/prog_tests/test_ima.c
> +++ b/tools/testing/selftests/bpf/prog_tests/test_ima.c
> @@ -9,6 +9,7 @@
> #include <unistd.h>
> #include <sys/wait.h>
> #include <test_progs.h>
> +#include <linux/ring_buffer.h>
>
> #include "ima.skel.h"
>
> @@ -31,9 +32,18 @@ static int run_measured_process(const char *measured_dir, u32 *monitored_pid)
> return -EINVAL;
> }
>
> +static u64 ima_hash_from_bpf;
> +
> +static int process_sample(void *ctx, void *data, size_t len)
> +{
> + ima_hash_from_bpf = *((u64 *)data);
> + return 0;
> +}
> +
> void test_test_ima(void)
> {
> char measured_dir_template[] = "/tmp/ima_measuredXXXXXX";
> + struct ring_buffer *ringbuf;
> const char *measured_dir;
> char cmd[256];
>
> @@ -44,6 +54,11 @@ void test_test_ima(void)
> if (CHECK(!skel, "skel_load", "skeleton failed\n"))
> goto close_prog;
>
> + ringbuf = ring_buffer__new(bpf_map__fd(skel->maps.ringbuf),
> + process_sample, NULL, NULL);
> + if (CHECK(!ringbuf, "ringbuf_create", "failed to create ringbuf\n"))
> + goto close_prog;
nit: could have used ASSERT_OK_PTR()
> +
> err = ima__attach(skel);
> if (CHECK(err, "attach", "attach failed: %d\n", err))
> goto close_prog;
> @@ -60,11 +75,9 @@ void test_test_ima(void)
> if (CHECK(err, "run_measured_process", "err = %d\n", err))
> goto close_clean;
>
> - CHECK(skel->data->ima_hash_ret < 0, "ima_hash_ret",
> - "ima_hash_ret = %ld\n", skel->data->ima_hash_ret);
> -
> - CHECK(skel->bss->ima_hash == 0, "ima_hash",
> - "ima_hash = %lu\n", skel->bss->ima_hash);
> + err = ring_buffer__poll(ringbuf, 1000);
nit: given data should definitely be available here, could use
ring_buffer__consume() instead and fail immediately if data is not
there
> + ASSERT_EQ(err, 1, "num_samples_or_err");
> + ASSERT_NEQ(ima_hash_from_bpf, 0, "ima_hash");
>
> close_clean:
> snprintf(cmd, sizeof(cmd), "./ima_setup.sh cleanup %s", measured_dir);
> diff --git a/tools/testing/selftests/bpf/progs/ima.c b/tools/testing/selftests/bpf/progs/ima.c
> index 86b21aff4bc5..dd0792204a21 100644
> --- a/tools/testing/selftests/bpf/progs/ima.c
> +++ b/tools/testing/selftests/bpf/progs/ima.c
> @@ -9,20 +9,37 @@
> #include <bpf/bpf_helpers.h>
> #include <bpf/bpf_tracing.h>
>
> -long ima_hash_ret = -1;
> -u64 ima_hash = 0;
> u32 monitored_pid = 0;
>
> +struct {
> + __uint(type, BPF_MAP_TYPE_RINGBUF);
> + __uint(max_entries, 1 << 12);
> +} ringbuf SEC(".maps");
> +
> char _license[] SEC("license") = "GPL";
>
> SEC("lsm.s/bprm_committed_creds")
> -int BPF_PROG(ima, struct linux_binprm *bprm)
> +void BPF_PROG(ima, struct linux_binprm *bprm)
> {
> - u32 pid = bpf_get_current_pid_tgid() >> 32;
> + u64 ima_hash = 0;
> + u64 *sample;
> + int ret;
> + u32 pid;
> +
> + pid = bpf_get_current_pid_tgid() >> 32;
> + if (pid == monitored_pid) {
> + ret = bpf_ima_inode_hash(bprm->file->f_inode, &ima_hash,
> + sizeof(ima_hash));
> + if (ret < 0 || ima_hash == 0)
> + return;
> +
> + sample = bpf_ringbuf_reserve(&ringbuf, sizeof(u64), 0);
> + if (!sample)
> + return;
>
> - if (pid == monitored_pid)
> - ima_hash_ret = bpf_ima_inode_hash(bprm->file->f_inode,
> - &ima_hash, sizeof(ima_hash));
> + *sample = ima_hash;
> + bpf_ringbuf_submit(sample, BPF_RB_FORCE_WAKEUP);
no need for BPF_RB_FORCE_WAKEUP, notification should happen
deterministically. And further, if you use ring_buffer__consume() you
won't even rely on notifications. Did you see any problems without
this?
> + }
>
> - return 0;
> + return;
> }
> --
> 2.30.0.365.g02bc693789-goog
>
next prev parent reply other threads:[~2021-02-04 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 23:23 [PATCH bpf-next 0/2] BPF Ringbuffer + Sleepable Programs KP Singh
2021-02-03 23:23 ` [PATCH bpf-next 1/2] bpf: Allow usage of BPF ringbuffer in sleepable programs KP Singh
2021-02-04 5:02 ` Andrii Nakryiko
2021-02-03 23:23 ` [PATCH bpf-next 2/2] bpf/selftests: Update the IMA test to use BPF ring buffer KP Singh
2021-02-04 4:59 ` Andrii Nakryiko [this message]
2021-02-04 18:46 ` KP Singh
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='CAEf4Bzb4LzUPkA0SB3W2iri42=4Pv3CveWb+-a6rAJU772HvQA@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jackmanb@chromium.org \
--cc=kpsingh@kernel.org \
--cc=revest@chromium.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).