Thread (13 messages) 13 messages, 7 authors, 2011-04-14

Re: [Bugme-new] [Bug 32832] New: shutdown(2) does not fully shut down socket any more

flat view

From: Cyril Bonté <hidden>
Date: 2011-04-13 07:06:31

Le mercredi 13 avril 2011 04:55:27, Eric Dumazet a écrit :
I worked on it this week end to discover FreeBSD 8.1 would not allow
several CLOSE sockets bound to same port even with REUSEADDR.
Just to complete the information, yes it does, but only after a shutdown() 
call. And this is the use case of haproxy, amavisd (quoted in the bugzilla bug 
report), and others.
So haproxy claim is a bit wrong (its trick doesnt work on FreeBSD), and
used an undocumented linux feature.
Both test cases (the one I provided to explain the haproxy issue and the one 
provided by Kees) are not about binding 2 sockets at the same time but binding 
a new socket after the first one has been shutdown.
Sadly this also looks undocumented on FreeBSD (only saw a reference on it in a 
code comment).
Since SO_REUSEPORT is not a 'stable fix', I suggest we revert the patch,
and eventually work on SO_REUSEPORT on net-next-2.6

What do you think ?
Agree.

Many thanks for the time you already spent on that.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help