RE: [Patch bpf-next v7 02/13] skmsg: introduce a spinlock to protect ingress_msg

2021-03-29 Thread John Fastabend
Cong Wang wrote: > From: Cong Wang > > Currently we rely on lock_sock to protect ingress_msg, > it is too big for this, we can actually just use a spinlock > to protect this list like protecting other skb queues. > > __tcp_bpf_recvmsg() is still special because of peeking, > it still has to use

[Patch bpf-next v7 02/13] skmsg: introduce a spinlock to protect ingress_msg

2021-03-28 Thread Cong Wang
From: Cong Wang Currently we rely on lock_sock to protect ingress_msg, it is too big for this, we can actually just use a spinlock to protect this list like protecting other skb queues. __tcp_bpf_recvmsg() is still special because of peeking, it still has to use lock_sock. Cc: John Fastabend C