Re: [bpf PATCH] bpf: avoid kcm psock use and tcp_bpf from colliding

On 08/30/2018 03:33 PM, John Fastabend wrote: > Currently we check sk_user_data is non NULL to determine if the sk > exists in a map. However, this is not sufficient to ensure the psock > is not in use by another (non-ULP TCP) user, such as kcm. To avoid > this when adding a sock to a map also veri

[bpf PATCH] bpf: avoid kcm psock use and tcp_bpf from colliding

Currently we check sk_user_data is non NULL to determine if the sk exists in a map. However, this is not sufficient to ensure the psock is not in use by another (non-ULP TCP) user, such as kcm. To avoid this when adding a sock to a map also verify it is of the correct ULP type. Signed-off-by: John