I'd ask the kernel Team to integrate the following changes into our 4.13 kernel release to avoid any sort of update-regressions related to SO_REUSEPORT [1]
- Reproducer [2] without libvirt, how to use in [3]
- Fixes are submitted as [3] - [6]
- If I tracked them correctly they went upstream without [5]+[6] but with [7] instead
- Overall the upstream change that I'd ask to pull in as a fix into any 4.13 release is in the merge [8] as part of 4.14-rc2
I'd ask the kernel Team to integrate the following changes into our 4.13 kernel release to avoid any sort of update-regressions related to SO_REUSEPORT [1]
- Reproducer [2] without libvirt, how to use in [3]
- Fixes are submitted as [3] - [6]
- If I tracked them correctly they went upstream without [5]+[6] but with [7] instead
- Overall the upstream change that I'd ask to pull in as a fix into any 4.13 release is in the merge [8] as part of 4.14-rc2
[1]: https:/ /lwn.net/ Articles/ 542629/ /bugzilla. redhat. com/attachment. cgi?id= 1314915 www.spinics. net/lists/ netdev/ msg454647. html www.spinics. net/lists/ netdev/ msg454769. html www.spinics. net/lists/ netdev/ msg454786. html www.spinics. net/lists/ netdev/ msg454933. html /github. com/torvalds/ linux/commit/ fbed24bcc69d3e4 8c5402c371f19f5 c7688871e5 /github. com/torvalds/ linux/commit/ 4e683f499a15cd7 77d3cb51aaebe48 d72334c852
[2]: https:/
[3]: http://
[4]: http://
[5]: http://
[6]: http://
[7]: https:/
[8]: https:/