On Tue, Aug 4, 2026 at 12:21 PM T.J. Mercier <[email protected]> wrote: > > In testing environments, binding to the port can transiently fail > > following a driver reset caused by the preceding queue configuration. > > The failing bind() is typically caused by DHCP/IPv6 DAD needing some > > time to resolve and assign the IP address back to the interface after > > the reset. > > With EADDRNOTAVAIL? Maybe loop only for that errno? >
I did not check the actual error code returned. I could. But is it worth maintaining an exact list of error codes to retry on for this test code? It will be annoying for the next guy to discover another error code that legitimately requires waiting, and then we'd have to maintain a list of error codes to retry on. It would be worth going through the trouble for actual kernel code, but it feels like more trouble than it's worth for a test? -- Thanks, Mina
