On Thu, Sep 6, 2018 at 9:58 AM Vincent Whitchurch <[email protected]> wrote: > > 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 f214f915e7db ("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: f214f915e7db ("tcp: enable MSG_ZEROCOPY") > > Signed-off-by: Vincent Whitchurch <[email protected]>
Acked-by: Willem de Bruijn <[email protected]> Good catch, thanks for fixing this. Please remember to mark patches with PATCH net
