[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1446640851.4184.20.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Wed, 04 Nov 2015 04:40:51 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Wolfgang Walter <linux@...m.de>
Cc: David Miller <davem@...emloft.net>, Jerry Chu <hkchu@...gle.com>,
JesseGross <jesse@...ira.com>, Tom Herbert <tom@...bertland.com>,
netdev <netdev@...r.kernel.org>, kernel-team@...com,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH net-next] ipv6: gro: support sit protocol
On Wed, 2015-11-04 at 13:19 +0100, Wolfgang Walter wrote:
> Today I found a problem: on a router forwarding GRE-packets (ipv4) (it is not
> the endpount) the interface (intel igb) stops sending packets after some time.
> I think this happens when an ISATAP packet is inside the GRE-packet.
>
> gre packets arrives on eth0
> eth1 stops sending (receiving still works)
> ethtool -r eth1
> eth1 works again for some time
>
> Switching GRO off on eth0 "fixes" the problem.
>
> I didn't test vanilla 4.1.12 yet, though. Until today 4.1.11 has been running
> on the router. What I tested was your patch
> "gre_gso_segment() chokes if SIT frames were aggregated by GRO engine."
> but did not solve the problem.
>
> So I would not recommend to backport it to longterm 4.1.
>
> My plans are:
>
> * test vanilla 4.1.12
> * test 4.3
>
> I want to test 4.3 on another router first, though.
If the NIC stops sending packets after some time, it might be an igb
issue.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists