From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
haoluo@google.com, jolsa@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 1/2] bpftool: mark orphaned programs during prog show
Date: Tue, 28 Nov 2023 02:30:26 +0000 [thread overview]
Message-ID: <170113862601.1467.14103892622059549472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231127182057.1081138-1-sdf@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 27 Nov 2023 10:20:56 -0800 you wrote:
> Commit ef01f4e25c17 ("bpf: restore the ebpf program ID for BPF_AUDIT_UNLOAD
> and PERF_BPF_EVENT_PROG_UNLOAD") stopped removing program's id from
> idr when the offloaded/bound netdev goes away. I was supposed to
> take a look and check in [0], but apparently I did not.
>
> Martin points out it might be useful to keep it that way for
> observability sake, but we at least need to mark those programs as
> unusable.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpftool: mark orphaned programs during prog show
https://git.kernel.org/bpf/bpf-next/c/876843ce1e48
- [bpf-next,v3,2/2] selftests/bpf: update test_offload to use new orphaned property
https://git.kernel.org/bpf/bpf-next/c/cf9791631027
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-28 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 18:20 [PATCH bpf-next v3 1/2] bpftool: mark orphaned programs during prog show Stanislav Fomichev
2023-11-27 18:20 ` [PATCH bpf-next v3 2/2] selftests/bpf: update test_offload to use new orphaned property Stanislav Fomichev
2023-11-27 22:42 ` [PATCH bpf-next v3 1/2] bpftool: mark orphaned programs during prog show Quentin Monnet
2023-11-28 2:30 ` patchwork-bot+netdevbpf [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=170113862601.1467.14103892622059549472.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--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 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.