From: Quentin Monnet <qmo@kernel.org>
To: Rong Tao <rtoax@foxmail.com>,
andrii.nakryiko@gmail.com, ast@kernel.org, daniel@iogearbox.net
Cc: Rong Tao <rongtao@cestc.cn>, Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
"open list:BPF [TOOLING] (bpftool)" <bpf@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next v3] bpftool: Check map name length when map create
Date: Wed, 12 Feb 2025 11:23:09 +0000 [thread overview]
Message-ID: <3541c732-9c7a-4de9-b658-c194fd52a361@kernel.org> (raw)
In-Reply-To: <tencent_AF066A426F591F977D2A73AF00A34A883808@qq.com>
2025-02-12 09:20 UTC+0800 ~ Rong Tao <rtoax@foxmail.com>
> From: Rong Tao <rongtao@cestc.cn>
>
> The size of struct bpf_map::name is BPF_OBJ_NAME_LEN (16).
>
> bpf(2) {
> map_create() {
> bpf_obj_name_cpy(map->name, attr->map_name, sizeof(attr->map_name));
> }
> }
>
> When specifying a map name using bpftool map create name, no error is
> reported if the name length is greater than 15.
>
> $ sudo bpftool map create /sys/fs/bpf/12345678901234567890 \
> type array key 4 value 4 entries 5 name 12345678901234567890
>
> Users will think that 12345678901234567890 is legal, but this name cannot
> be used to index a map.
>
> $ sudo bpftool map show name 12345678901234567890
> Error: can't parse name
>
> $ sudo bpftool map show
> ...
> 1249: array name 123456789012345 flags 0x0
> key 4B value 4B max_entries 5 memlock 304B
>
> $ sudo bpftool map show name 123456789012345
> 1249: array name 123456789012345 flags 0x0
> key 4B value 4B max_entries 5 memlock 304B
>
> The map name provided in the command line is truncated, but no warning is
> reported. This submission checks the length of the map name.
>
> Reviewed-by: Quentin Monnet <qmo@kernel.org>
> Signed-off-by: Rong Tao <rongtao@cestc.cn>
> ---
> v2: https://lore.kernel.org/lkml/tencent_26592A2BAF08A3A688A50600421559929708@qq.com/
> v1: https://lore.kernel.org/lkml/tencent_1C4444032C2188ACD04B4995B0D78F510607@qq.com/
> ---
> tools/bpf/bpftool/map.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tools/bpf/bpftool/map.c b/tools/bpf/bpftool/map.c
> index ed4a9bd82931..9617e64d3d11 100644
> --- a/tools/bpf/bpftool/map.c
> +++ b/tools/bpf/bpftool/map.c
> @@ -1270,6 +1270,10 @@ static int do_create(int argc, char **argv)
> } else if (is_prefix(*argv, "name")) {
> NEXT_ARG();
> map_name = GET_ARG();
> + if (strlen(map_name) > BPF_OBJ_NAME_LEN - 1) {
> + p_info("Warning: map name is longer than %d characters, it will be truncated.\n",
Change looks mostly good, thanks! Two small things to address with this
message string:
- Please remove the trailing '\n', p_info() adds it already.
- Please replace %d with %u. The value is unsigned, and we've merged a
commit to clean these up recently, 17c3dc50294b ("bpftool: Using the
right format specifiers").
> + BPF_OBJ_NAME_LEN - 1);
> + }
> } else if (is_prefix(*argv, "key")) {
> if (parse_u32_arg(&argc, &argv, &key_size,
> "key size"))
prev parent reply other threads:[~2025-02-12 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 1:20 [PATCH bpf-next v3] bpftool: Check map name length when map create Rong Tao
2025-02-12 11:23 ` Quentin Monnet [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=3541c732-9c7a-4de9-b658-c194fd52a361@kernel.org \
--to=qmo@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@fomichev.me \
--cc=song@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.