From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: mcgrof@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, asavkov@redhat.com, bpf@vger.kernel.org,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@chromium.org, sdf@google.com,
haoluo@google.com, pmladek@suse.com, thunder.leizhen@huawei.com,
vmalik@redhat.com
Subject: Re: [PATCH bpf-next] kallsyms: Disable preemption for find_kallsyms_symbol_value
Date: Wed, 05 Apr 2023 00:20:17 +0000 [thread overview]
Message-ID: <168065401700.950.3027124778713262383.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230403220254.2191240-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 4 Apr 2023 00:02:54 +0200 you wrote:
> Artem reported suspicious RCU usage [1]. The reason is that verifier
> calls find_kallsyms_symbol_value with preemption enabled which will
> trigger suspicious RCU usage warning in rcu_dereference_sched call.
>
> Disabling preemption in find_kallsyms_symbol_value and adding
> __find_kallsyms_symbol_value function.
>
> [...]
Here is the summary with links:
- [bpf-next] kallsyms: Disable preemption for find_kallsyms_symbol_value
https://git.kernel.org/bpf/bpf-next/c/d099f594ad56
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:[~2023-04-05 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 22:02 [PATCH bpf-next] kallsyms: Disable preemption for find_kallsyms_symbol_value Jiri Olsa
2023-04-04 1:43 ` Leizhen (ThunderTown)
2023-04-04 6:56 ` Artem Savkov
2023-04-05 0:20 ` patchwork-bot+netdevbpf [this message]
2023-04-06 14:47 ` Petr Mladek
2023-04-06 14:56 ` Aaron Tomlin
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=168065401700.950.3027124778713262383.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=pmladek@suse.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=thunder.leizhen@huawei.com \
--cc=vmalik@redhat.com \
--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.