On Mon, Sep 17, 2018 at 10:32 AM John Fastabend <[email protected]> wrote: > > After this patch we only allow socks that are in ESTABLISHED state or > are being added via a sock_ops event that is transitioning into an > ESTABLISHED state. By allowing sock_ops events we allow users to > manage sockmaps directly from sock ops programs. The two supported > sock_ops ops are BPF_SOCK_OPS_PASSIVE_ESTABLISHED_CB and > BPF_SOCK_OPS_ACTIVE_ESTABLISHED_CB. > > Similar to TLS ULP this ensures sk_user_data is correct. > > Reported-by: Eric Dumazet <[email protected]> > Fixes: 1aa12bdf1bfb ("bpf: sockmap, add sock close() hook to remove socks") > Signed-off-by: John Fastabend <[email protected]>
Acked-by: Yonghong Song <[email protected]>
