diff options
author | Willem de Bruijn <willemb@google.com> | 2019-05-30 18:01:21 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-05-30 15:54:04 -0700 |
commit | 100f6d8e09905c59be45b6316f8f369c0be1b2d8 (patch) | |
tree | 4d3161cefeea7f8ff4dc614a5d0140dd29bd7793 /tools | |
parent | b73484b2fc0d0ba84a13e9d86eb4adcae718163b (diff) | |
download | linux-stable-100f6d8e09905c59be45b6316f8f369c0be1b2d8.tar.gz linux-stable-100f6d8e09905c59be45b6316f8f369c0be1b2d8.tar.bz2 linux-stable-100f6d8e09905c59be45b6316f8f369c0be1b2d8.zip |
net: correct zerocopy refcnt with udp MSG_MORE
TCP zerocopy takes a uarg reference for every skb, plus one for the
tcp_sendmsg_locked datapath temporarily, to avoid reaching refcnt zero
as it builds, sends and frees skbs inside its inner loop.
UDP and RAW zerocopy do not send inside the inner loop so do not need
the extra sock_zerocopy_get + sock_zerocopy_put pair. Commit
52900d22288ed ("udp: elide zerocopy operation in hot path") introduced
extra_uref to pass the initial reference taken in sock_zerocopy_alloc
to the first generated skb.
But, sock_zerocopy_realloc takes this extra reference at the start of
every call. With MSG_MORE, no new skb may be generated to attach the
extra_uref to, so refcnt is incorrectly 2 with only one skb.
Do not take the extra ref if uarg && !tcp, which implies MSG_MORE.
Update extra_uref accordingly.
This conditional assignment triggers a false positive may be used
uninitialized warning, so have to initialize extra_uref at define.
Changes v1->v2: fix typo in Fixes SHA1
Fixes: 52900d22288e7 ("udp: elide zerocopy operation in hot path")
Reported-by: syzbot <syzkaller@googlegroups.com>
Diagnosed-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions