From: Yonghong Song <yonghong.song@linux.dev>
To: Artem Savkov <asavkov@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, netdev@vger.kernel.org, jolsa@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: fix potential premature unload in bpf_testmod
Date: Tue, 9 Jan 2024 11:40:38 -0800 [thread overview]
Message-ID: <82f55c0e-0ec8-4fe1-8d8c-b1de07558ad9@linux.dev> (raw)
In-Reply-To: <20240109164317.16371-1-asavkov@redhat.com>
On 1/9/24 8:43 AM, Artem Savkov 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").
>
> Fixes: 65eb006d85a2a ("bpf: Move kernel test kfuncs to bpf_testmod")
Please add your Signed-off-by tag.
I think the root cause is that bpf_kfunc_call_test_acquire() kfunc
is defined in bpf_testmod and the kfunc returns some data in bpf_testmod.
But the release function bpf_kfunc_call_test_release() is in the kernel.
The release func tries to access some data in bpf_testmod which might
have been unloaded. The prog_test_ref_kfunc is defined in the kernel, so
no bpf_testmod btf reference is hold so bpf_testmod can be unloaded before
bpf_kfunc_call_test_release().
As you mentioned, we won't have this issue if bpf_kfunc_call_test_acquire()
is also in the kernel.
I think putting bpf_kfunc_call_test_acquire() in bpf_testmod and
bpf_kfunc_call_test_release() in kernel is not a good idea and confusing.
But since this is only for tests, I guess we can live with that. With that,
Acked-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c b/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c
> index 91907b321f913..63f0dbd016703 100644
> --- a/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c
> +++ b/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c
> @@ -2,6 +2,7 @@
> /* Copyright (c) 2020 Facebook */
> #include <linux/btf.h>
> #include <linux/btf_ids.h>
> +#include <linux/delay.h>
> #include <linux/error-injection.h>
> #include <linux/init.h>
> #include <linux/module.h>
> @@ -544,6 +545,9 @@ static int bpf_testmod_init(void)
>
> static void bpf_testmod_exit(void)
> {
> + while (refcount_read(&prog_test_struct.cnt) > 1)
> + msleep(20);
> +
> return sysfs_remove_bin_file(kernel_kobj, &bin_attr_bpf_testmod_file);
> }
>
next prev parent reply other threads:[~2024-01-09 19:40 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 [this message]
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
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=82f55c0e-0ec8-4fe1-8d8c-b1de07558ad9@linux.dev \
--to=yonghong.song@linux.dev \
--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 \
/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).