On Wed, Aug 5, 2026 at 10:36 AM Mina Almasry <[email protected]> wrote: > > 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?
My thinking is it's also annoying to have to wait 10s for an error condition that cannot be recovered from. I don't feel strongly.
