From: Martin KaFai Lau <martin.lau@linux.dev>
To: Feng zhou <zhoufeng.zf@bytedance.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
yangzhenze@bytedance.com, wangdongdong.6@bytedance.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org
Subject: Re: [PATCH bpf-next] bpf: getsockopt hook to get optval without checking kernel retval
Date: Wed, 31 May 2023 22:37:52 -0700 [thread overview]
Message-ID: <5bc1ac0d-cea8-19e5-785a-cd72140d8cdb@linux.dev> (raw)
In-Reply-To: <20230601024900.22902-1-zhoufeng.zf@bytedance.com>
On 5/31/23 7:49 PM, Feng zhou wrote:
> From: Feng Zhou <zhoufeng.zf@bytedance.com>
>
> Remove the judgment on retval and pass bpf ctx by default. The
> advantage of this is that it is more flexible. Bpf getsockopt can
> support the new optname without using the module to call the
> nf_register_sockopt to register.
>
> Signed-off-by: Feng Zhou <zhoufeng.zf@bytedance.com>
> ---
> kernel/bpf/cgroup.c | 35 +++++++++++++----------------------
> 1 file changed, 13 insertions(+), 22 deletions(-)
>
> diff --git a/kernel/bpf/cgroup.c b/kernel/bpf/cgroup.c
> index 5b2741aa0d9b..ebad5442d8bb 100644
> --- a/kernel/bpf/cgroup.c
> +++ b/kernel/bpf/cgroup.c
> @@ -1896,30 +1896,21 @@ int __cgroup_bpf_run_filter_getsockopt(struct sock *sk, int level,
> if (max_optlen < 0)
> return max_optlen;
>
> - if (!retval) {
> - /* If kernel getsockopt finished successfully,
> - * copy whatever was returned to the user back
> - * into our temporary buffer. Set optlen to the
> - * one that kernel returned as well to let
> - * BPF programs inspect the value.
> - */
> -
> - if (get_user(ctx.optlen, optlen)) {
> - ret = -EFAULT;
> - goto out;
> - }
> + if (get_user(ctx.optlen, optlen)) {
> + ret = -EFAULT;
> + goto out;
> + }
>
> - if (ctx.optlen < 0) {
> - ret = -EFAULT;
> - goto out;
> - }
> - orig_optlen = ctx.optlen;
> + if (ctx.optlen < 0) {
> + ret = -EFAULT;
> + goto out;
> + }
> + orig_optlen = ctx.optlen;
>
> - if (copy_from_user(ctx.optval, optval,
> - min(ctx.optlen, max_optlen)) != 0) {
> - ret = -EFAULT;
> - goto out;
> - }
> + if (copy_from_user(ctx.optval, optval,
> + min(ctx.optlen, max_optlen)) != 0) {
What is in optval that is useful to copy from if the kernel didn't handle the
optname?
and there is no selftest also.
> + ret = -EFAULT;
> + goto out;
> }
>
> lock_sock(sk);
next prev parent reply other threads:[~2023-06-01 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 2:49 [PATCH bpf-next] bpf: getsockopt hook to get optval without checking kernel retval Feng zhou
2023-06-01 5:37 ` Martin KaFai Lau [this message]
2023-06-01 6:05 ` Feng Zhou
2023-06-01 15:50 ` Martin KaFai Lau
2023-06-06 3:20 ` Feng Zhou
2023-06-06 17:04 ` Stanislav Fomichev
2023-06-08 3:39 ` Feng Zhou
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=5bc1ac0d-cea8-19e5-785a-cd72140d8cdb@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--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=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=wangdongdong.6@bytedance.com \
--cc=yangzhenze@bytedance.com \
--cc=yhs@fb.com \
--cc=zhoufeng.zf@bytedance.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