Re: Stable request
From: David Miller <davem@davemloft.net>
Date: 2019-10-16 17:47:49
Also in:
linux-sctp
From: Edward Cree <redacted> Date: Wed, 16 Oct 2019 16:26:50 +0100
On 04/10/2019 16:17, Edward Cree wrote:quoted
On 23/08/2019 22:42, David Miller wrote:quoted
From: Xin Long <lucien.xin@gmail.com> Date: Fri, 23 Aug 2019 19:33:03 +0800quoted
We need a similar fix for ipv6 as Commit 0761680d5215 ("net: ipv4: fix listify ip_rcv_finish in case of forwarding") does for ipv4. This issue can be reprocuded by syzbot since Commit 323ebb61e32b ("net: use listified RX for handling GRO_NORMAL skbs") on net-next. The call trace was:...quoted
Fixes: d8269e2cbf90 ("net: ipv6: listify ipv6_rcv() and ip6_rcv_finish()") Fixes: 323ebb61e32b ("net: use listified RX for handling GRO_NORMAL skbs") Reported-by: syzbot+eb349eeee854e389c36d@syzkaller.appspotmail.com Reported-by: syzbot+4a0643a653ac375612d1@syzkaller.appspotmail.com Signed-off-by: Xin Long <lucien.xin@gmail.com>Applied, thanks.Just noticed that this only went to net-next (and 5.4-rc1), when actually it's needed on all kernels back to 4.19 (per the first Fixes: tag). The second Fixes: reference, 323ebb61e32b, merely enables syzbot to hit it on whatever hardware it has, but the bug was already there, and hittable on sfc NICs. David, can this go to stable please?Hi, did this get missed or was my request improper in some way?
Sorry, I'm just getting over a cold and very backlogged on this kind of stuff. I'll get to this while I can Ed.