sock: remove zerocopy sockopt restriction on closed tcp state
authorWillem de Bruijn <willemb@google.com>
Wed, 14 Mar 2018 16:49:19 +0000 (12:49 -0400)
committerDavid S. Miller <davem@davemloft.net>
Wed, 14 Mar 2018 16:51:28 +0000 (12:51 -0400)
commitced68234b6a244355aeab07c2681bc49f695eaed
tree38f43d6e42f562bcae799dae9238502a086cf785
parent29d1df72ce2ac187d457990fe445a16212dcfa19
sock: remove zerocopy sockopt restriction on closed tcp state

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@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Documentation/networking/msg_zerocopy.rst
net/core/sock.c