> On Dec 19, 2016, at 9:42 PM, Eric Dumazet <eric.duma...@gmail.com> wrote: > >> On Mon, 2016-12-19 at 18:07 -0800, Tom Herbert wrote: >> >> When sockets created SO_REUSEPORT move to TW state they are placed >> back on the the tb->owners. fastreuse port is no longer set so we have >> to walk potential long list of sockets in tb->owners to open a new >> listener socket. I imagine this is happens when we try to open a new >> listener SO_REUSEPORT after the system has been running a while and so >> we hit the long tb->owners list. > > Hmm... __inet_twsk_hashdance() does not change tb->fastreuse > > So where tb->fastreuse is cleared ? > > If all your sockets have SO_REUSEPORT set, this should not happen. >
The app starts out with no SO_REUSEPORT, and then we restart it with that option enabled. What I suspect is we have all the twsks from the original service, and the fastreuse stuff is cleared. My naive patch resets it once we add a reuseport sk to the tb and that makes the problem go away. I'm reworking all of this logic and adding some extra info to the tb to make the reset actually safe. I'll send those patches out tomorrow. Thanks, Josef
