From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v2] bpf: Add necessary migrate_{disable,enable} in range_tree
Date: Fri, 15 Nov 2024 16:20:29 +0000 [thread overview]
Message-ID: <173168762925.2635622.6673990600725223564.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241115060354.2832495-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 14 Nov 2024 22:03:54 -0800 you wrote:
> When running bpf selftest (./test_progs -j), the following warnings
> showed up:
>
> $ ./test_progs -t arena_atomics
> ...
> BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u19:0/12501
> caller is bpf_mem_free+0x128/0x330
> ...
> Call Trace:
> <TASK>
> dump_stack_lvl
> check_preemption_disabled
> bpf_mem_free
> range_tree_destroy
> arena_map_free
> bpf_map_free_deferred
> process_scheduled_works
> ...
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: Add necessary migrate_{disable,enable} in range_tree
https://git.kernel.org/bpf/bpf-next/c/4ff04abf9d5b
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:[~2024-11-15 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 6:03 [PATCH bpf-next v2] bpf: Add necessary migrate_{disable,enable} in range_tree Yonghong Song
2024-11-15 16:20 ` 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=173168762925.2635622.6673990600725223564.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=kernel-team@fb.com \
--cc=martin.lau@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