From: Byeonguk Jeong <jungbu2855@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Yonghong Song <yonghong.song@linux.dev>,
bpf <bpf@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/bpf: Add test for trie_get_next_key()
Date: Fri, 25 Oct 2024 07:26:37 +0900 [thread overview]
Message-ID: <ZxrJnZ4+hmZ90Mbj@localhost.localdomain> (raw)
In-Reply-To: <d94bf8c7-b026-4608-83d7-6230f136ee3b@iogearbox.net>
Hi Daniel,
Okay, I will submit them in a series of patches. Btw, ASSERT_* macros
are not defined for map_tests. Should I add the definitions for them,
or just go with CHECK?
Thanks,
Byeonguk
On Thu, Oct 24, 2024 at 11:41:19AM +0200, Daniel Borkmann wrote:
> Hi Byeonguk,
>
> On 10/24/24 11:08 AM, Byeonguk Jeong wrote:
> > Add a test for out-of-bounds write in trie_get_next_key() when a full
> > path from root to leaf exists and bpf_map_get_next_key() is called
> > with the leaf node. It may crashes the kernel on failure, so please
> > run in a VM.
> >
> > Signed-off-by: Byeonguk Jeong <jungbu2855@gmail.com>
>
> Could you submit the fix + this selftest as a 2-patch series, otherwise BPF CI
> cannot test both in combination (pls make sure subject has [PATCH bpf] so that
> our CI adds this on top of the bpf tree).
>
> Right now the CI selftest build threw an error:
>
> /tmp/work/bpf/bpf/tools/testing/selftests/bpf/map_tests/lpm_trie_map_get_next_key.c: In function ‘test_lpm_trie_map_get_next_key’:
> /tmp/work/bpf/bpf/tools/testing/selftests/bpf/map_tests/lpm_trie_map_get_next_key.c:84:9: error: format not a string literal and no format arguments [-Werror=format-security]
> 84 | CHECK(map_fd == -1, "bpf_map_create(), error:%s\n",
> | ^~~~~
> TEST-OBJ [test_maps] task_storage_map.test.o
> TEST-OBJ [test_progs] access_variable_array.test.o
> cc1: all warnings being treated as errors
> TEST-OBJ [test_progs] align.test.o
> TEST-OBJ [test_progs] arena_atomics.test.o
> make: *** [Makefile:765: /tmp/work/bpf/bpf/tools/testing/selftests/bpf/lpm_trie_map_get_next_key.test.o] Error 1
> make: *** Waiting for unfinished jobs....
> GEN-SKEL [test_progs-no_alu32] test_usdt.skel.h
> make: Leaving directory '/tmp/work/bpf/bpf/tools/testing/selftests/bpf'
>
> Also on quick glance, please use ASSERT_*() macros instead of CHECK() as the
> latter is deprecated.
>
> Thanks,
> Daniel
next prev parent reply other threads:[~2024-10-24 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 1:45 [PATCH] bpf: Fix out-of-bounds write in trie_get_next_key() Byeonguk Jeong
2024-10-22 9:43 ` Toke Høiland-Jørgensen
2024-10-22 19:51 ` Alexei Starovoitov
2024-10-23 1:29 ` Byeonguk Jeong
2024-10-23 8:44 ` Byeonguk Jeong
2024-10-23 2:03 ` Hou Tao
2024-10-23 7:30 ` Byeonguk Jeong
2024-10-23 9:59 ` Hou Tao
2024-10-24 1:48 ` Byeonguk Jeong
2024-10-24 3:19 ` Hou Tao
2024-10-24 9:08 ` [PATCH] selftests/bpf: Add test for trie_get_next_key() Byeonguk Jeong
2024-10-24 9:41 ` Daniel Borkmann
2024-10-24 22:26 ` Byeonguk Jeong [this message]
2024-10-25 11:54 ` Hou Tao
2024-10-25 12:03 ` Daniel Borkmann
2024-10-25 11:53 ` Hou Tao
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=ZxrJnZ4+hmZ90Mbj@localhost.localdomain \
--to=jungbu2855@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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.