From: Neil Horman <nhorman@xxxxxxxxxxxxx> Date: Tue, 10 Dec 2013 06:48:15 -0500 > 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@xxxxxxxxxxxxx> > Acked-by: Vlad Yasevich <vyasevich@xxxxxxxxx> Applied, thanks Neil. -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
