lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 30 Apr 2020 22:54:35 -0700 From: Martin KaFai Lau <kafai@...com> To: Stanislav Fomichev <sdf@...gle.com> CC: <netdev@...r.kernel.org>, <bpf@...r.kernel.org>, <davem@...emloft.net>, <ast@...nel.org>, <daniel@...earbox.net>, John Fastabend <john.fastabend@...il.com> Subject: Re: [PATCH bpf-next v3] bpf: bpf_{g,s}etsockopt for struct bpf_sock_addr On Thu, Apr 30, 2020 at 04:31:52PM -0700, Stanislav Fomichev wrote: > Currently, bpf_getsockopt and bpf_setsockopt helpers operate on the > 'struct bpf_sock_ops' context in BPF_PROG_TYPE_SOCK_OPS program. > Let's generalize them and make them available for 'struct bpf_sock_addr'. > That way, in the future, we can allow those helpers in more places. > > As an example, let's expose those 'struct bpf_sock_addr' based helpers to > BPF_CGROUP_INET{4,6}_CONNECT hooks. That way we can override CC before the > connection is made. > > v3: > * Expose custom helpers for bpf_sock_addr context instead of doing > generic bpf_sock argument (as suggested by Daniel). Even with > try_socket_lock that doesn't sleep we have a problem where context sk > is already locked and socket lock is non-nestable. Acked-by: Martin KaFai Lau <kafai@...com>
Powered by blists - more mailing lists