skbuff: fix incorrect msg_zerocopy copy notifications
authorWillem de Bruijn <willemb@google.com>
Wed, 9 Jun 2021 22:41:57 +0000 (18:41 -0400)
committerDavid S. Miller <davem@davemloft.net>
Thu, 10 Jun 2021 20:39:57 +0000 (13:39 -0700)
commit3bdd5ee0ec8c14131d560da492e6df452c6fdd75
tree7570089040ba20cd29843991e4bdd5c35a0812b9
parent388fa7f13d61074ba3aaedce0f47ff92441c0b1a
skbuff: fix incorrect msg_zerocopy copy notifications

msg_zerocopy signals if a send operation required copying with a flag
in serr->ee.ee_code.

This field can be incorrect as of the below commit, as a result of
both structs uarg and serr pointing into the same skb->cb[].

uarg->zerocopy must be read before skb->cb[] is reinitialized to hold
serr. Similar to other fields len, hi and lo, use a local variable to
temporarily hold the value.

This was not a problem before, when the value was passed as a function
argument.

Fixes: 75518851a2a0 ("skbuff: Push status and refcounts into sock_zerocopy_callback")
Reported-by: Talal Ahmad <talalahmad@google.com>
Signed-off-by: Willem de Bruijn <willemb@google.com>
Acked-by: Soheil Hassas Yeganeh <soheil@google.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/core/skbuff.c