linux-kernel - Re: [RESEND PATCH] bpftool: Support use full prog name in prog subcommand

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1f124efa-ac5b-5a50-2efe-243f4405a314@linux.alibaba.com>
Date:   Wed, 2 Nov 2022 20:55:27 +0800
From:   Tao Chen <chentao.kernel@...ux.alibaba.com>
To:     Quentin Monnet <quentin@...valent.com>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii@...nel.org>,
        Martin KaFai Lau <martin.lau@...ux.dev>,
        Song Liu <song@...nel.org>, Yonghong Song <yhs@...com>,
        John Fastabend <john.fastabend@...il.com>,
        KP Singh <kpsingh@...nel.org>,
        Stanislav Fomichev <sdf@...gle.com>
Cc:     bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] bpftool: Support use full prog name in prog
 subcommand

在 2022/11/2 下午7:56, Quentin Monnet 写道:
> 2022-11-02 10:35 UTC+0800 ~ Tao Chen <chentao.kernel@...ux.alibaba.com>
>> Now that the commit: <b662000aff84> ("bpftool: Adding support for BTF
>> program names") supported show the full prog name, we can also use
>> the full prog name more than 16 (BPF_OBJ_NAME_LEN) chars in prog
>> subcommand, such as "bpftool prog show name PROG_NAME".
>>
>> Signed-off-by: Tao Chen <chentao.kernel@...ux.alibaba.com>
> 
> Thanks! But you mean you want something like this, correct?
> 
> 	# ./bpftool prog pin \
> 		name prog_with_a_very_long_name /sys/fs/bpf/foo
> 
> This is already possible since commit d55dfe587bc0 ("bpftool: Remove
> BPF_OBJ_NAME_LEN restriction when looking up bpf program by name"). Your
> first version of the patch was based on a version that didn't have this
> commit, but bpftool from bpf-next already supports this.
> 
> Quentin
Yes, sorry my branch is a little behind，please ignore this patch, thank 
you for your reply!