[Patch bpf-next v8 01/16] skmsg: lock ingress_skb when purging

[Cong Wang]

From: Cong Wang <cong.w...@bytedance.com>

Currently we purge the ingress_skb queue only when psock
refcnt goes down to 0, so locking the queue is not necessary,
but in order to be called during ->close, we have to lock it
here.

Cc: John Fastabend <john.fastab...@gmail.com>
Cc: Daniel Borkmann <dan...@iogearbox.net>
Cc: Lorenz Bauer <l...@cloudflare.com>
Acked-by: Jakub Sitnicki <ja...@cloudflare.com>
Signed-off-by: Cong Wang <cong.w...@bytedance.com>
---
 net/core/skmsg.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net/core/skmsg.c b/net/core/skmsg.c
index 07f54015238a..bebf84ed4e30 100644
--- a/net/core/skmsg.c
+++ b/net/core/skmsg.c
@@ -634,7 +634,7 @@ static void sk_psock_zap_ingress(struct sk_psock *psock)
 {
        struct sk_buff *skb;
 
-       while ((skb = __skb_dequeue(&psock->ingress_skb)) != NULL) {
+       while ((skb = skb_dequeue(&psock->ingress_skb)) != NULL) {
                skb_bpf_redirect_clear(skb);
                kfree_skb(skb);
        }
-- 
2.25.1