netdev - Re: [PATCH net-next] sock: remove zerocopy sockopt restriction on closed tcp state

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]

Message-Id: <20180314.125201.1978223315979430694.davem@davemloft.net>
Date:   Wed, 14 Mar 2018 12:52:01 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     willemdebruijn.kernel@...il.com
Cc:     netdev@...r.kernel.org, soheil@...gle.com, kou@...ich.ibm.com,
        willemb@...gle.com
Subject: Re: [PATCH net-next] sock: remove zerocopy sockopt restriction on
 closed tcp state

From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Date: Wed, 14 Mar 2018 12:49:19 -0400

> From: Willem de Bruijn <willemb@...gle.com>
> 
> Socket option SO_ZEROCOPY determines whether the kernel ignores or
> processes flag MSG_ZEROCOPY on subsequent send calls. This to avoid
> changing behavior for legacy processes.
> 
> Limiting the state change to closed sockets is annoying with passive
> sockets and not necessary for correctness. Once created, zerocopy skbs
> are processed based on their private state, not this socket flag.
> 
> Remove the constraint.
> 
> Signed-off-by: Willem de Bruijn <willemb@...gle.com>

Applied, thanks Willem.