Message ID | 1490059683-13884-1-git-send-email-fgao@ikuai8.com |
---|---|
State | Accepted, archived |
Delegated to: | David Miller |
Headers | show |
From: fgao@ikuai8.com Date: Tue, 21 Mar 2017 09:28:03 +0800 > From: Gao Feng <fgao@ikuai8.com> > > When user_mss is zero, it means use the default value. But the current > codes don't permit user set TCP_MAXSEG to the default value. > It would return the -EINVAL when val is zero. > > Signed-off-by: Gao Feng <fgao@ikuai8.com> > --- > v3: Correct the logic error, per Neal > v2: Make codes more clearer, per Eric > v1: initial version Applied to net-next, thanks.
diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c index 1e319a5..4f7f163 100644 --- a/net/ipv4/tcp.c +++ b/net/ipv4/tcp.c @@ -2470,7 +2470,7 @@ static int do_tcp_setsockopt(struct sock *sk, int level, /* Values greater than interface MTU won't take effect. However * at the point when this call is done we typically don't yet * know which interface is going to be used */ - if (val < TCP_MIN_MSS || val > MAX_TCP_WINDOW) { + if (val && (val < TCP_MIN_MSS || val > MAX_TCP_WINDOW)) { err = -EINVAL; break; }