summaryrefslogtreecommitdiff
path: root/Documentation/ja_JP
diff options
context:
space:
mode:
authorNeil Horman <nhorman@tuxdriver.com>2013-12-10 06:48:15 -0500
committerDavid S. Miller <davem@davemloft.net>2013-12-10 22:41:26 -0500
commit9f70f46bd4c7267d48ef461a1d613ec9ec0d520c (patch)
tree440b75235bac97bb649d020f3b74f1ff84183ecd /Documentation/ja_JP
parent231df15f1ccbbb4526fdbcf072059b661b48c07d (diff)
sctp: properly latch and use autoclose value from sock to association
Currently, sctp associations latch a sockets autoclose value to an association at association init time, subject to capping constraints from the max_autoclose sysctl value. This leads to an odd situation where an application may set a socket level autoclose timeout, but sliently sctp will limit the autoclose timeout to something less than that. Fix this by modifying the autoclose setsockopt function to check the limit, cap it and warn the user via syslog that the timeout is capped. This will allow getsockopt to return valid autoclose timeout values that reflect what subsequent associations actually use. While were at it, also elimintate the assoc->autoclose variable, it duplicates whats in the timeout array, which leads to multiple sources for the same information, that may differ (as the former isn't subject to any capping). This gives us the timeout information in a canonical place and saves some space in the association structure as well. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Vlad Yasevich <vyasevich@gmail.com> CC: Wang Weidong <wangweidong1@huawei.com> CC: David Miller <davem@davemloft.net> CC: Vlad Yasevich <vyasevich@gmail.com> CC: netdev@vger.kernel.org Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/ja_JP')
0 files changed, 0 insertions, 0 deletions