[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <YvU2md/W4YSlnkBH@google.com>
Date: Thu, 11 Aug 2022 10:04:25 -0700
From: sdf@...gle.com
To: Martin KaFai Lau <kafai@...com>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org,
Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
David Miller <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, kernel-team@...com,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH v3 bpf-next 00/15] bpf: net: Remove duplicated code from bpf_setsockopt()
On 08/10, Martin KaFai Lau wrote:
> The code in bpf_setsockopt() is mostly a copy-and-paste from
> the sock_setsockopt(), do_tcp_setsockopt(), do_ipv6_setsockopt(),
> and do_ip_setsockopt(). As the allowed optnames in bpf_setsockopt()
> grows, so are the duplicated code. The code between the copies
> also slowly drifted.
> This set is an effort to clean this up and reuse the existing
> {sock,do_tcp,do_ipv6,do_ip}_setsockopt() as much as possible.
> After the clean up, this set also adds a few allowed optnames
> that we need to the bpf_setsockopt().
> The initial attempt was to clean up both bpf_setsockopt() and
> bpf_getsockopt() together. However, the patch set was getting
> too long. It is beneficial to leave the bpf_getsockopt()
> out for another patch set. Thus, this set is focusing
> on the bpf_setsockopt().
> v3:
> - s/in_bpf/has_current_bpf_ctx/ (Andrii)
> - Add comments to has_current_bpf_ctx() and sockopt_lock_sock()
> (Stanislav)
> - Use vmlinux.h in selftest and add defines to bpf_tracing_net.h
> (Stanislav)
> - Use bpf_getsockopt(SO_MARK) in selftest (Stanislav)
> - Use BPF_CORE_READ_BITFIELD in selftest (Yonghong)
Reviewed-by: Stanislav Fomichev <sdf@...gle.com>
(I didn't go super deep on the selftest)
Powered by blists - more mailing lists