public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: tunnels: Don't apply GRO to multiple layers of encapsulation.
@ 2017-08-31 13:58 joe.korty
  2017-09-02  3:40 ` Jesse Gross
  0 siblings, 1 reply; 3+ messages in thread
From: joe.korty @ 2017-08-31 13:58 UTC (permalink / raw)
  To: Jesse Gross; +Cc: linux-kernel

[ resend due to mail problems at my end ]

Hi Jesse,

The backport of fac8e0f579695a3ecbc4d3cac369139d7f819971,
"tunnels: Don't apply GRO to multiple layers of encapsulation",
to linux-4.1.y seems to have missed a line.

The 4.1 commit is 066b300e5be43cb61697539e2a3a9aac5afb422f.

The potentially missing line is:

-               .gro_receive    = ipv6_gro_receive,
+               .gro_receive    = sit_gro_receive,


I am not experiencing any bad symptoms.  I simply noticed
that the patch introduced a new function, sit_gro_receive,
without introducing any users, and that same patch in  
linux-4.4.y does have a user.

Regards,
Joe

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: tunnels: Don't apply GRO to multiple layers of encapsulation.
@ 2017-09-05 14:08 joe.korty
  0 siblings, 0 replies; 3+ messages in thread
From: joe.korty @ 2017-09-05 14:08 UTC (permalink / raw)
  To: Sasha Levin; +Cc: Jesse Gross, LKML

Hi Sasha,
The backport of

   fac8e0f579695a3ecbc4d3cac369139d7f819971
   tunnels: Don't apply GRO to multiple layers of encapsulation

into 4.1 missed a hunk.  The same backport into 3.18 was done
correctly.  This patch introduces the missing hunk into 4.1.
Excepts from some emails:

Joe Korty wrote:
> I am not experiencing any bad symptoms.  I simply noticed
> that the patch introduced a new function, sit_gro_receive,
> without introducing any users, and that same patch in
> linux-4.4.y does have a user.

Jesse gross wrote:
> Thanks for pointing that out. The line you mentioned
> should indeed be there and seems to have been missed in
> the backport.
> 
> The backport was actually done by Sasha, not by me -
> would you mind sending a patch to him or working with him
> to fix it?

Could you review this and run it through your tests and
send it along to Greg if appropriate?

Thanks,
Joe

Signed-off-by: Joe Korty <joe.korty@concurrent-rt.com>

Index: b/net/ipv6/ip6_offload.c
===================================================================
--- a/net/ipv6/ip6_offload.c
+++ b/net/ipv6/ip6_offload.c
@@ -300,7 +300,7 @@ static struct packet_offload ipv6_packet
 	.type = cpu_to_be16(ETH_P_IPV6),
 	.callbacks = {
 		.gso_segment = ipv6_gso_segment,
-		.gro_receive = ipv6_gro_receive,
+		.gro_receive = sit_gro_receive,
 		.gro_complete = ipv6_gro_complete,
 	},
 };

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-09-05 14:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-31 13:58 tunnels: Don't apply GRO to multiple layers of encapsulation joe.korty
2017-09-02  3:40 ` Jesse Gross
  -- strict thread matches above, loose matches on Subject: below --
2017-09-05 14:08 joe.korty

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox