On Wed, 2018-01-24 at 12:35 -0800, Tom Herbert wrote: > This is needed to prevent sk_user_data being overwritten. > The check is done under the callback lock. This should prevent > a socket from being attached twice to a KCM mux. It also prevents > a socket from being attached for other use cases of sk_user_data > as long as the other cases set sk_user_data under the lock. > Followup work is needed to unify all the use cases of sk_user_data > to use the same locking. >
Reviewed-by: Eric Dumazet <eduma...@google.com>
