From: patchwork-bot+netdevbpf@kernel.org
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@chromium.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] bpf: propagate __user annotations properly
Date: Tue, 08 Dec 2020 03:30:06 +0000 [thread overview]
Message-ID: <160739820678.1788.12048920183003808630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201207123720.19111-1-lukas.bulwahn@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Mon, 7 Dec 2020 13:37:20 +0100 you wrote:
> __htab_map_lookup_and_delete_batch() stores a user pointer in the local
> variable ubatch and uses that in copy_{from,to}_user(), but ubatch misses a
> __user annotation.
>
> So, sparse warns in the various assignments and uses of ubatch:
>
> kernel/bpf/hashtab.c:1415:24: warning: incorrect type in initializer
> (different address spaces)
> kernel/bpf/hashtab.c:1415:24: expected void *ubatch
> kernel/bpf/hashtab.c:1415:24: got void [noderef] __user *
>
> [...]
Here is the summary with links:
- bpf: propagate __user annotations properly
https://git.kernel.org/bpf/bpf-next/c/2f4b03195fe8
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:[~2020-12-08 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 12:37 [PATCH] bpf: propagate __user annotations properly Lukas Bulwahn
2020-12-07 12:37 ` Lukas Bulwahn
2020-12-07 16:12 ` Yonghong Song
2020-12-07 16:12 ` Yonghong Song
2020-12-07 16:28 ` Lukas Bulwahn
2020-12-07 16:28 ` Lukas Bulwahn
2020-12-08 3:30 ` 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=160739820678.1788.12048920183003808630.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=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.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.