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>
This commit is contained in:
committed by
David S. Miller
parent
29d1df72ce
commit
ced68234b6
@@ -1052,8 +1052,6 @@ set_rcvbuf:
|
||||
if (sk->sk_family == PF_INET || sk->sk_family == PF_INET6) {
|
||||
if (sk->sk_protocol != IPPROTO_TCP)
|
||||
ret = -ENOTSUPP;
|
||||
else if (sk->sk_state != TCP_CLOSE)
|
||||
ret = -EBUSY;
|
||||
} else if (sk->sk_family != PF_RDS) {
|
||||
ret = -ENOTSUPP;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user