netdev - Re: [PATCH net v3 1/1] net: tcp: Permit user set TCP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 22 Mar 2017 11:48:13 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     fgao@...ai8.com
Cc:     kuznet@....inr.ac.ru, jmorris@...ei.org, eric.dumazet@...il.com,
        netdev@...r.kernel.org, gfree.wind@...il.com
Subject: Re: [PATCH net v3 1/1] net: tcp: Permit user set TCP_MAXSEG to
 default value

From: fgao@...ai8.com
Date: Tue, 21 Mar 2017 09:28:03 +0800

> From: Gao Feng <fgao@...ai8.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@...ai8.com>
> ---
>  v3: Correct the logic error, per Neal
>  v2: Make codes more clearer, per Eric
>  v1: initial version

Applied to net-next, thanks.