On 06/27/2018 07:02 AM, Magnus Karlsson wrote: > There was a potential race in the TX completion code for > the SKB case when the TX napi thread and the error path > of the sendmsg code could both call the SKB destructor > at the same time. Fixed by introducing a spin_lock in the > destructor. Wow, what is the impact on performance ? Please describe a bit more what is the problem.
- [PATCH bpf 0/4] Bug fixes to the SKB TX path of AF_XDP Magnus Karlsson
- [PATCH bpf 3/4] samples/bpf: deal with EBUSY return c... Magnus Karlsson
- [PATCH bpf 2/4] xsk: frame could be completed more th... Magnus Karlsson
- [PATCH bpf 1/4] xsk: fix potential lost completion me... Magnus Karlsson
- [PATCH bpf 4/4] xsk: fix potential race in SKB TX com... Magnus Karlsson
- Re: [PATCH bpf 4/4] xsk: fix potential race in SK... Eric Dumazet
- Re: [PATCH bpf 4/4] xsk: fix potential race i... Daniel Borkmann
- Re: [PATCH bpf 4/4] xsk: fix potential race i... Magnus Karlsson