Re: [PATCH net v2 1/1] net: tcp: Permit user set TCP_MAXSEG to default value

2017-03-20 Thread Feng Gao
On Tue, Mar 21, 2017 at 9:23 AM, Neal Cardwell wrote: > On Mon, Mar 20, 2017 at 8:45 PM, wrote: >> 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, i

Re: [PATCH net v2 1/1] net: tcp: Permit user set TCP_MAXSEG to default value

2017-03-20 Thread Neal Cardwell
On Mon, Mar 20, 2017 at 8:45 PM, wrote: > 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 M

[PATCH net v2 1/1] net: tcp: Permit user set TCP_MAXSEG to default value

2017-03-20 Thread fgao
From: Gao Feng 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 --- v2: Make codes more clearer, per Eric v1: initial version net/ipv4/tcp