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
..
datagram.c
dev_addr_lists.c
dev_ioctl.c
dev.c	notifier: Remove notifier header file wherever not used	2018-08-30 12:56:40 +02:00
devlink.c
drop_monitor.c
dst_cache.c
dst.c
ethtool.c
failover.c
fib_notifier.c
fib_rules.c
filter.c	bpf: Fix bpf_msg_pull_data()	2018-09-02 22:29:53 +02:00
flow_dissector.c
gen_estimator.c
gen_stats.c
gro_cells.c
hwbm.c
link_watch.c
lwt_bpf.c
lwtunnel.c
Makefile
neighbour.c
net_namespace.c
net-procfs.c
net-sysfs.c
net-sysfs.h
net-traces.c
netclassid_cgroup.c
netevent.c
netpoll.c
netprio_cgroup.c
page_pool.c
pktgen.c
ptp_classifier.c
request_sock.c
rtnetlink.c	net: rtnl: return early from rtnl_unregister_all when protocol isn't registered	2018-08-29 19:28:55 -07:00
scm.c
secure_seq.c
skbuff.c	tcp: really ignore MSG_ZEROCOPY if no SO_ZEROCOPY	2018-09-07 23:11:06 -07:00
sock_diag.c
sock_reuseport.c
sock.c
stream.c
sysctl_net_core.c
timestamping.c
tso.c
utils.c
xdp.c