[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181027.214426.537959459795607171.davem@davemloft.net>
Date: Sat, 27 Oct 2018 21:44:26 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: oleksandr@...alenko.name
Cc: dave.taht@...il.com, hkallweit1@...il.com, toke@...e.dk,
jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: CAKE and r8169 cause panic on upload in v4.19
From: Oleksandr Natalenko <oleksandr@...alenko.name>
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);
}
Powered by blists - more mailing lists