From: Oleksandr Natalenko <redacted>
Date: Fri, 26 Oct 2018 22:54:12 +0200
Next, I've seen GRO bits in the call trace and decided to disable GRO
on this NIC. So far, I cannot trigger a panic with GRO disabled even
after 20 rounds of speedtest.
So, must be some generic thing indeed.
Yeah something is out-of-whack with GRO.
Does this fix it?
diff --git a/net/core/dev.c b/net/core/dev.c
index 022ad73d6253..77d43ae2a7bb 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -5457,7 +5457,7 @@ static void gro_flush_oldest(struct list_head *head)
/* Do not adjust napi->gro_hash[].count, caller is adding a new
* SKB to the chain.
*/
- list_del(&oldest->list);
+ skb_list_del_init(oldest);
napi_gro_complete(oldest);
}