like the issue discussed e.g. here: > > https://www.mail-archive.com/netdev@xxxxxxxxxxxxxxx/msg232633.html > Yes, that does! > Could you check if 4.18.x or 4.19-rc2 kernel behaves differently? > I just finished checking that earlier this afternoon. I can confirm that 4.18 does not have the problem. 4.17.19 has the problem. So, the fix was introduced in 4.18. I am in the process of compiling my own kernel so I can prove that that particular commit was indeed the fix. > If you could confirm that the commit above (with its prerequisities) > resolves the issue, it may be possible to backport it to the > distribution kernel. I tried to backport it to our 4.4 based kernel and > it wasn't very hard, backporting to 4.15 based one should be easier. > That would be excellent. :)
