summaryrefslogtreecommitdiff
path: root/arch/sparc
diff options
context:
space:
mode:
authorWillem de Bruijn <willemb@google.com>2017-12-28 12:38:13 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-01-02 20:31:13 +0100
commitb9edd6bf0ccb2939a7716b80d3e73a24ead9fe62 (patch)
treefec700c00050e98551ccae46fa1cf31865413fc6 /arch/sparc
parent49cd180d4a104159f240a9a896e5f13844227378 (diff)
skbuff: in skb_copy_ubufs unclone before releasing zerocopy
skb_copy_ubufs must unclone before it is safe to modify its skb_shared_info with skb_zcopy_clear. Commit b90ddd568792 ("skbuff: skb_copy_ubufs must release uarg even without user frags") ensures that all skbs release their zerocopy state, even those without frags. But I forgot an edge case where such an skb arrives that is cloned. The stack does not build such packets. Vhost/tun skbs have their frags orphaned before cloning. TCP skbs only attach zerocopy state when a frag is added. But if TCP packets can be trimmed or linearized, this might occur. Tracing the code I found no instance so far (e.g., skb_linearize ends up calling skb_zcopy_clear if !skb->data_len). Still, it is non-obvious that no path exists. And it is fragile to rely on this. Fixes: b90ddd568792 ("skbuff: skb_copy_ubufs must release uarg even without user frags") Signed-off-by: Willem de Bruijn <willemb@google.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/sparc')
0 files changed, 0 insertions, 0 deletions