@@ -199,6 +199,7 @@ struct vfs_ns_cap_data {
/* Allow multicasting */
/* Allow read/write of device-specific registers */
/* Allow activation of ATM control sockets */
+/* Allow setting TCP_LINGER2 regardless of sysctl_tcp_fin_timeout */
#define CAP_NET_ADMIN 12
@@ -128,6 +128,7 @@ enum {
#define TCP_CM_INQ TCP_INQ
#define TCP_TX_DELAY 37 /* delay outgoing packets by XX usec */
+#define TCP_FORCE_LINGER2 38 /* Set TCP_LINGER2 regardless of sysctl_tcp_fin_timeout */
#define TCP_REPAIR_ON 1
@@ -3149,6 +3149,15 @@ static int do_tcp_setsockopt(struct sock *sk, int level,
tcp_enable_tx_delay();
tp->tcp_tx_delay = val;
break;
+ case TCP_FORCE_LINGER2:
+ if (val < 0)
+ tp->linger2 = -1;
+ else if (val > net->ipv4.sysctl_tcp_fin_timeout / HZ &&
+ !ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN))
+ tp->linger2 = 0;
+ else
+ tp->linger2 = val * HZ;
+ break;
default:
err = -ENOPROTOOPT;
break;
This patch adds a new TCP socket option named TCP_FORCE_LINGER2. The option has same behavior as TCP_LINGER2, except the tp->linger2 value can be greater than sysctl_tcp_fin_timeout if the user_ns is capable with CAP_NET_ADMIN. As a server, different sockets may need different FIN-WAIT timeout and in most cases the system default value will be used. The timeout can be adjusted by setting TCP_LINGER2 but cannot be greater than the system default value. If one socket needs a timeout greater than the default, we have to adjust the sysctl which affects all sockets using the system default value. And if we want to adjust it for just one socket and keep the original value for others, all the other sockets have to set TCP_LINGER2. But with TCP_FORCE_LINGER2, the net admin can set greater tp->linger2 than the default for one socket and keep the sysctl_tcp_fin_timeout unchanged. Signed-off-by: Cambda Zhu <cambda@linux.alibaba.com> --- include/uapi/linux/capability.h | 1 + include/uapi/linux/tcp.h | 1 + net/ipv4/tcp.c | 9 +++++++++ 3 files changed, 11 insertions(+)