From: Tao Chen <chentao.kernel@linux.alibaba.com>
To: Quentin Monnet <quentin@isovalent.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] bpftool: Support use full prog name in prog subcommand
Date: Wed, 2 Nov 2022 20:55:27 +0800 [thread overview]
Message-ID: <1f124efa-ac5b-5a50-2efe-243f4405a314@linux.alibaba.com> (raw)
In-Reply-To: <6927ffa1-e7f5-6691-dc86-da6c0d628c4f@isovalent.com>
在 2022/11/2 下午7:56, Quentin Monnet 写道:
> 2022-11-02 10:35 UTC+0800 ~ Tao Chen <chentao.kernel@linux.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@linux.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!
prev parent reply other threads:[~2022-11-02 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 2:35 [RESEND PATCH] bpftool: Support use full prog name in prog subcommand Tao Chen
2022-11-02 11:56 ` Quentin Monnet
2022-11-02 12:55 ` Tao Chen [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=1f124efa-ac5b-5a50-2efe-243f4405a314@linux.alibaba.com \
--to=chentao.kernel@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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