[Bugme-new] [Bug 32832] New: shutdown(2) does not fully shut down socket any more
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Wed Apr 6 15:42:38 PDT 2011
https://bugzilla.kernel.org/show_bug.cgi?id=32832
Summary: shutdown(2) does not fully shut down socket any more
Product: Networking
Version: 2.5
Kernel Version: 2.6.38
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
AssignedTo: shemminger at linux-foundation.org
ReportedBy: kees at outflux.net
Regression: Yes
In 2.6.35 and earlier, shutdown(2) will fully remove a socket. This does not
appear to be true any more and is causing software to misbehave.
2.6.35:
$ ./testcase
parent: 5957
before:
tcp 0 0 0.0.0.0:12345 0.0.0.0:* LISTEN
after:
child: 5961
$ ./testcase
parent: 6001
before:
tcp 0 0 0.0.0.0:12345 0.0.0.0:* LISTEN
after:
child: 6002
2.6.38:
$ ./testcase
parent: 1138
before:
tcp 0 0 0.0.0.0:12345 0.0.0.0:* LISTEN
after:
child: 1142
$ ./testcase
bind: Address already in use
The listener doesn't show up in netstat any more, but as long as the child
process is running, the socket is unavailable. It is as if the shutdown(2)
behavior has partially reverted to close(2) behavior (but in the case of using
close(2), the child's socket would remain visible in netstat).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Bugme-new
mailing list