Files
android_kernel_xiaomi_sm8450/net/ipv4
Vincent Whitchurch 5cf4a8532c tcp: really ignore MSG_ZEROCOPY if no SO_ZEROCOPY
According to the documentation in msg_zerocopy.rst, the SO_ZEROCOPY
flag was introduced because send(2) ignores unknown message flags and
any legacy application which was accidentally passing the equivalent of
MSG_ZEROCOPY earlier should not see any new behaviour.

Before commit f214f915e7 ("tcp: enable MSG_ZEROCOPY"), a send(2) call
which passed the equivalent of MSG_ZEROCOPY without setting SO_ZEROCOPY
would succeed.  However, after that commit, it fails with -ENOBUFS.  So
it appears that the SO_ZEROCOPY flag fails to fulfill its intended
purpose.  Fix it.

Fixes: f214f915e7 ("tcp: enable MSG_ZEROCOPY")
Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
Acked-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2018-09-07 23:11:06 -07:00
..
2018-05-16 07:24:30 +02:00
2017-10-21 01:33:19 +01:00
2018-04-23 10:21:24 -04:00
2018-07-07 10:58:49 +09:00
2018-03-27 13:18:09 -04:00
2018-06-22 13:43:27 +09:00
2018-07-24 14:10:43 -07:00
2017-10-16 21:24:25 +01:00
2018-02-28 11:43:28 -05:00