From: patchwork-bot+netdevbpf@kernel.org
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
live-patching@vger.kernel.org, daniel@iogearbox.net,
kernel-team@fb.com, jolsa@kernel.org, rostedt@goodmis.org,
andrii@kernel.org
Subject: Re: [PATCH bpf-next] bpf: fix test_progs -j error with fentry/fexit tests
Date: Fri, 29 Jul 2022 21:40:13 +0000 [thread overview]
Message-ID: <165913081322.32307.9736154924263103124.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220729194106.1207472-1-song@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 29 Jul 2022 12:41:06 -0700 you wrote:
> Then multiple threads are attaching/detaching fentry/fexit programs to
> the same trampoline, we may call register_fentry on the same trampoline
> twice: register_fentry(), unregister_fentry(), then register_fentry again.
> This causes ftrace_set_filter_ip() for the same ip on tr->fops twice,
> which leaves duplicated ip in tr->fops. The extra ip is not cleaned up
> properly on unregister and thus causes failures with further register in
> register_ftrace_direct_multi():
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: fix test_progs -j error with fentry/fexit tests
https://git.kernel.org/bpf/bpf-next/c/dc81f8d1e8ea
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:[~2022-07-29 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 19:41 [PATCH bpf-next] bpf: fix test_progs -j error with fentry/fexit tests Song Liu
2022-07-29 19:43 ` Steven Rostedt
2022-07-29 21:40 ` 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=165913081322.32307.9736154924263103124.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=song@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).