From: patchwork-bot+netdevbpf@kernel.org
To: Artem Savkov <asavkov@redhat.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org, jolsa@kernel.org,
linux-kernel@vger.kernel.org, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v2] selftests/bpf: fix potential premature unload in bpf_testmod
Date: Tue, 16 Jan 2024 15:50:30 +0000 [thread overview]
Message-ID: <170542023010.19641.12554162884652194073.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240110085737.8895-1-asavkov@redhat.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 10 Jan 2024 09:57:37 +0100 you wrote:
> It is possible for bpf_kfunc_call_test_release() to be called from
> bpf_map_free_deferred() when bpf_testmod is already unloaded and
> perf_test_stuct.cnt which it tries to decrease is no longer in memory.
> This patch tries to fix the issue by waiting for all references to be
> dropped in bpf_testmod_exit().
>
> The issue can be triggered by running 'test_progs -t map_kptr' in 6.5,
> but is obscured in 6.6 by d119357d07435 ("rcu-tasks: Treat only
> synchronous grace periods urgently").
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: fix potential premature unload in bpf_testmod
https://git.kernel.org/bpf/bpf-next/c/6ad61815babf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-01-16 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 16:43 [PATCH bpf-next] selftests/bpf: fix potential premature unload in bpf_testmod Artem Savkov
2024-01-09 19:40 ` Yonghong Song
2024-01-10 8:14 ` Artem Savkov
2024-01-10 12:49 ` Jiri Olsa
2024-01-10 8:57 ` [PATCH bpf-next v2] " Artem Savkov
2024-01-16 15:50 ` patchwork-bot+netdevbpf [this message]
2024-01-16 16:58 ` Jiri Olsa
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=170542023010.19641.12554162884652194073.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=asavkov@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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).