On 08.05.23 09:40, Greg KH wrote: > On Mon, May 08, 2023 at 07:33:58AM +0000, Rai, Anjali wrote: >> >> We have one test which test the functionality of "using the same loopback address and port for both IPV6 and IPV4", The test should result in EADDRINUSE for binding IPv4 to same port, but it was successful >> >> Test Description: >> The test creates sockets for both IPv4 and IPv6, and forces IPV6 to listen for both IPV4 and IPV6 connections; this in turn makes binding another (IPV4) socket on the same port meaningless and results in -EADDRINUSE >> >> Our systems had Kernel v6.0.9 and the test was successfully executing, we recently upgraded our systems to v6.2, and we saw this as a failure. The systems which are not upgraded, there it is still passing. >> >> We don't exactly at which point this test broke, but our assumption is https://github.com/torvalds/linux/commit/28044fc1d4953b07acec0da4d2fc4784c57ea6fb > > Is there a specific reason you did not add cc: for the authors of that > commit? > >> Can you please check on your end whether this is an actual regression of a feature request. > > If you revert that commit, does it resolve the issue? Have you worked > with the Intel networking developers to help debug this further? FWIW: that commit you mentioned above indeed caused a regression in a test, but the issue was fixed before 6.2 was released -- or at least it is supposed to. For details see: https://lore.kernel.org/all/6b971a4e-c7d8-411e-1f92-fda29b5b2fb9@xxxxxxxxxx/ Ciao, Thorsten
