From: Yonghong Song <yhs@fb.com>
To: Di Zhu <zhudi2@huawei.com>, <davem@davemloft.net>,
<ast@kernel.org>, <daniel@iogearbox.net>, <andrii@kernel.org>,
<kafai@fb.com>, <songliubraving@fb.com>,
<john.fastabend@gmail.com>, <kpsingh@kernel.org>,
<jakub@cloudflare.com>
Cc: <bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next v5 1/2] bpf: support BPF_PROG_QUERY for progs attached to sockmap
Date: Thu, 4 Nov 2021 21:23:51 -0700 [thread overview]
Message-ID: <ef670dc7-e3c9-ad89-dc8b-5cbd1910b38c@fb.com> (raw)
In-Reply-To: <20211105015730.1605333-1-zhudi2@huawei.com>
On 11/4/21 6:57 PM, Di Zhu wrote:
> Right now there is no way to query whether BPF programs are
> attached to a sockmap or not.
>
> we can use the standard interface in libbpf to query, such as:
> bpf_prog_query(mapFd, BPF_SK_SKB_STREAM_PARSER, 0, NULL, ...);
> the mapFd is the fd of sockmap.
>
> Signed-off-by: Di Zhu <zhudi2@huawei.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2021-11-05 4:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 1:57 [PATCH bpf-next v5 1/2] bpf: support BPF_PROG_QUERY for progs attached to sockmap Di Zhu
2021-11-05 1:57 ` [PATCH bpf-next v5 2/2] selftests: bpf: test " Di Zhu
2021-11-05 4:24 ` Yonghong Song
2021-11-05 4:23 ` Yonghong Song [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-15 2:38 [PATCH bpf-next v5 1/2] bpf: support " zhudi (E)
2022-01-15 2:53 ` Andrii Nakryiko
2022-01-15 19:09 ` Jakub Sitnicki
2022-01-14 5:44 zhudi (E)
2022-01-13 9:00 Di Zhu
2022-01-13 16:15 ` Jakub Sitnicki
2022-01-15 1:22 ` Andrii Nakryiko
2021-11-08 2:13 zhudi (E)
2021-11-04 6:35 zhudi (E)
2021-11-04 6:07 zhudi (E)
2021-11-04 6:30 ` Yonghong Song
2021-11-04 1:07 Di Zhu
2021-11-04 5:31 ` Yonghong Song
2021-11-05 19:51 ` Cong Wang
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=ef670dc7-e3c9-ad89-dc8b-5cbd1910b38c@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=zhudi2@huawei.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;
as well as URLs for NNTP newsgroup(s).