[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164864701147.1602.6890084343658807023.git-patchwork-notify@kernel.org>
Date: Wed, 30 Mar 2022 13:30:11 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jiri Olsa <jolsa@...nel.org>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org, kafai@...com,
songliubraving@...com, yhs@...com, john.fastabend@...il.com,
kpsingh@...omium.org
Subject: Re: [PATCH] bpf: Fix sparse warnings in kprobe_multi_resolve_syms
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Wed, 30 Mar 2022 13:05:10 +0200 you wrote:
> Adding missing __user tags to fix sparse warnings:
>
> kernel/trace/bpf_trace.c:2370:34: warning: incorrect type in argument 2 (different address spaces)
> kernel/trace/bpf_trace.c:2370:34: expected void const [noderef] __user *from
> kernel/trace/bpf_trace.c:2370:34: got void const *usyms
> kernel/trace/bpf_trace.c:2376:51: warning: incorrect type in argument 2 (different address spaces)
> kernel/trace/bpf_trace.c:2376:51: expected char const [noderef] __user *src
> kernel/trace/bpf_trace.c:2376:51: got char const *
> kernel/trace/bpf_trace.c:2443:49: warning: incorrect type in argument 1 (different address spaces)
> kernel/trace/bpf_trace.c:2443:49: expected void const *usyms
> kernel/trace/bpf_trace.c:2443:49: got void [noderef] __user *[assigned] usyms
>
> [...]
Here is the summary with links:
- bpf: Fix sparse warnings in kprobe_multi_resolve_syms
https://git.kernel.org/bpf/bpf/c/d31e0386a2f1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists