From: Martynas Pumputis <m@lambda.lt>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH bpf 2/2] selftests/bpf: check inner map deletion
Date: Fri, 16 Jul 2021 17:09:43 +0200 [thread overview]
Message-ID: <4b29412c-b8f2-39a2-4d96-4c1fa0360927@lambda.lt> (raw)
In-Reply-To: <CAEf4BzbP6Dr0GWavhV-MUqdFe1rB_A_criwHB_=yS_yGuoc1oQ@mail.gmail.com>
On 7/16/21 7:35 AM, Andrii Nakryiko wrote:
> On Wed, Jul 14, 2021 at 9:52 AM Martynas Pumputis <m@lambda.lt> wrote:
>>
>> Add a test case to check whether an unsuccessful creation of an outer
>> map of a BTF-defined map-in-map destroys the inner map.
>>
>> As bpf_object__create_map() is a static function, we cannot just call it
>> from the test case and then check whether a map accessible via
>> map->inner_map_fd has been removed. Instead, we iterate over all maps
>> and check whether the map "$MAP_NAME.inner" does not exist.
>>
>> Signed-off-by: Martynas Pumputis <m@lambda.lt>
>> ---
>> .../bpf/progs/test_map_in_map_invalid.c | 27 +++++++++
>> tools/testing/selftests/bpf/test_maps.c | 58 ++++++++++++++++++-
>> 2 files changed, 84 insertions(+), 1 deletion(-)
>> create mode 100644 tools/testing/selftests/bpf/progs/test_map_in_map_invalid.c
>>
>> diff --git a/tools/testing/selftests/bpf/progs/test_map_in_map_invalid.c b/tools/testing/selftests/bpf/progs/test_map_in_map_invalid.c
>> new file mode 100644
>> index 000000000000..03601779e4ed
>> --- /dev/null
>> +++ b/tools/testing/selftests/bpf/progs/test_map_in_map_invalid.c
>> @@ -0,0 +1,27 @@
>> +// SPDX-License-Identifier: GPL-2.0
>> +/* Copyright (c) 2021 Isovalent, Inc. */
>> +#include <linux/bpf.h>
>> +#include <bpf/bpf_helpers.h>
>> +
>> +struct inner {
>> + __uint(type, BPF_MAP_TYPE_ARRAY);
>> + __type(key, __u32);
>> + __type(value, int);
>> + __uint(max_entries, 4);
>> +};
>> +
>> +struct {
>> + __uint(type, BPF_MAP_TYPE_ARRAY_OF_MAPS);
>> + __uint(max_entries, 0); /* This will make map creation to fail */
>> + __uint(key_size, sizeof(__u32));
>> + __array(values, struct inner);
>> +} mim SEC(".maps");
>> +
>> +SEC("xdp_noop")
>> +int xdp_noop0(struct xdp_md *ctx)
>> +{
>> + return XDP_PASS;
>> +}
>> +
>> +int _version SEC("version") = 1;
>
> please don't add new uses of version, it's completely unnecessary on
> modern kernels
Sure.
>
>> +char _license[] SEC("license") = "GPL";
>> diff --git a/tools/testing/selftests/bpf/test_maps.c b/tools/testing/selftests/bpf/test_maps.c
>> index 30cbf5d98f7d..48f6c6dfd188 100644
>> --- a/tools/testing/selftests/bpf/test_maps.c
>> +++ b/tools/testing/selftests/bpf/test_maps.c
>> @@ -1153,12 +1153,16 @@ static void test_sockmap(unsigned int tasks, void *data)
>> }
>>
>> #define MAPINMAP_PROG "./test_map_in_map.o"
>> +#define MAPINMAP_INVALID_PROG "./test_map_in_map_invalid.o"
>> static void test_map_in_map(void)
>> {
>> struct bpf_object *obj;
>> struct bpf_map *map;
>> int mim_fd, fd, err;
>> int pos = 0;
>> + struct bpf_map_info info = {};
>> + __u32 len = sizeof(info);
>> + __u32 id = 0;
>>
>> obj = bpf_object__open(MAPINMAP_PROG);
>>
>> @@ -1229,10 +1233,62 @@ static void test_map_in_map(void)
>>
>> close(fd);
>> bpf_object__close(obj);
>> +
>> +
>> + /* Test that failing bpf_object__create_map() destroys the inner map */
>> +
>> + obj = bpf_object__open(MAPINMAP_INVALID_PROG);
>
> you didn't check bpf_object__open() succeeded here...
For the sake of brevity, I didn't add the check. If the opening fails,
then we will catch it anyway with the bpf_object__find_map_by_name()
invocation below: it will log "libbpf: elf: failed to open $PROG_NAME:
No such file or directory" and then segfault.
>
>> +
>> + map = bpf_object__find_map_by_name(obj, "mim");
>
> ... and crash will happen here on error
>
>> + if (!map) {
>> + printf("Failed to load array of maps from test prog\n");
>> + goto out_map_in_map;
>> + }
>> +
>
> [...]
>
next prev parent reply other threads:[~2021-07-16 15:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 16:54 [PATCH bpf 0/2] libbpf: fix inner map removal in bpf_object__create_map Martynas Pumputis
2021-07-14 16:54 ` [PATCH bpf 1/2] libbpf: fix removal of inner map " Martynas Pumputis
2021-07-15 0:30 ` John Fastabend
2021-07-15 10:06 ` Martynas Pumputis
2021-07-15 19:59 ` John Fastabend
2021-07-16 3:06 ` John Fastabend
2021-07-16 3:09 ` John Fastabend
2021-07-16 5:27 ` Andrii Nakryiko
2021-07-16 15:24 ` Martynas Pumputis
2021-07-14 16:54 ` [PATCH bpf 2/2] selftests/bpf: check inner map deletion Martynas Pumputis
2021-07-16 3:11 ` John Fastabend
2021-07-16 5:35 ` Andrii Nakryiko
2021-07-16 15:09 ` Martynas Pumputis [this message]
2021-07-16 18:24 ` Andrii Nakryiko
-- strict thread matches above, loose matches on Subject: below --
2021-07-19 17:38 [PATCH v2 bpf 0/2] libbpf: fix inner map removal in bpf_object__create_map Martynas Pumputis
2021-07-19 17:38 ` [PATCH bpf 2/2] selftests/bpf: check inner map deletion Martynas Pumputis
2021-07-19 22:59 ` Andrii Nakryiko
2021-07-20 20:24 ` Andrii Nakryiko
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=4b29412c-b8f2-39a2-4d96-4c1fa0360927@lambda.lt \
--to=m@lambda.lt \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
/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).