From: Yonghong Song <yhs@fb.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] bpf: propagate __user annotations properly
Date: Mon, 7 Dec 2020 08:12:05 -0800 [thread overview]
Message-ID: <480e9a0f-0a27-aec2-e8c6-a73b46069ba8@fb.com> (raw)
In-Reply-To: <20201207123720.19111-1-lukas.bulwahn@gmail.com>
On 12/7/20 4:37 AM, Lukas Bulwahn 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 *
>
> kernel/bpf/hashtab.c:1444:46: warning: incorrect type in argument 2
> (different address spaces)
> kernel/bpf/hashtab.c:1444:46: expected void const [noderef] __user *from
> kernel/bpf/hashtab.c:1444:46: got void *ubatch
>
> kernel/bpf/hashtab.c:1608:16: warning: incorrect type in assignment
> (different address spaces)
> kernel/bpf/hashtab.c:1608:16: expected void *ubatch
> kernel/bpf/hashtab.c:1608:16: got void [noderef] __user *
>
> kernel/bpf/hashtab.c:1609:26: warning: incorrect type in argument 1
> (different address spaces)
> kernel/bpf/hashtab.c:1609:26: expected void [noderef] __user *to
> kernel/bpf/hashtab.c:1609:26: got void *ubatch
>
> Add the __user annotation to repair this chain of propagating __user
> annotations in __htab_map_lookup_and_delete_batch().
Add fix tag?
Fixes: 057996380a42 ("bpf: Add batch ops to all htab bpf map")
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Thanks for the fix. LGTM. I guess either bpf or bpf-next tree is fine
since this is not a correctness issue.
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2020-12-07 16:13 UTC|newest]
Thread overview: 4+ 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 16:12 ` Yonghong Song [this message]
2020-12-07 16:28 ` Lukas Bulwahn
2020-12-08 3:30 ` patchwork-bot+netdevbpf
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=480e9a0f-0a27-aec2-e8c6-a73b46069ba8@fb.com \
--to=yhs@fb.com \
--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 \
/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