Comment 18 for bug 1924298

I wrote to Ricardo Diaz & Eric Dumazet to ask if the patch for this bug would be backported and it looks like the fix was made for the Linux stable kernels very recently: https://www.spinics.net/lists/stable-commits/msg244651.html

Eric Dumazet also mentioned that:
"the bug only happens if networking configuration is not optimal. (We never hit the bug at Google) Normally, all packets for a given 4-tuple should be handled by the same cpu. On multi-queues NIC, RSS ensures this, if only one cpu is servicing interrupts for any receive queue. Otherwise, cpus compete over the same spinlocks, and could hit the race that Ricardo fixed. I suggest you also work on networking configuration, as this could help even without this race, but once flows are established."

He suggested looking at `Documentation/networking/scaling.rst` as a starting point for tackling the network configuration.