diff options
author | Eric Dumazet <edumazet@google.com> | 2022-02-01 07:52:54 +0100 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2022-02-02 05:21:40 +0100 |
commit | 479f5547239d970d3833f15f54a6481fffdb91ec (patch) | |
tree | 524d5d9fedeea8d2594e0b7bdb9f524da541143a /crypto | |
parent | af_packet: fix data-race in packet_setsockopt / packet_setsockopt (diff) | |
download | linux-479f5547239d970d3833f15f54a6481fffdb91ec.tar.xz linux-479f5547239d970d3833f15f54a6481fffdb91ec.zip |
tcp: fix mem under-charging with zerocopy sendmsg()
We got reports of following warning in inet_sock_destruct()
WARN_ON(sk_forward_alloc_get(sk));
Whenever we add a non zero-copy fragment to a pure zerocopy skb,
we have to anticipate that whole skb->truesize will be uncharged
when skb is finally freed.
skb->data_len is the payload length. But the memory truesize
estimated by __zerocopy_sg_from_iter() is page aligned.
Fixes: 9b65b17db723 ("net: avoid double accounting for pure zerocopy skbs")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Talal Ahmad <talalahmad@google.com>
Cc: Arjun Roy <arjunroy@google.com>
Cc: Willem de Bruijn <willemb@google.com>
Acked-by: Soheil Hassas Yeganeh <soheil@google.com>
Link: https://lore.kernel.org/r/20220201065254.680532-1-eric.dumazet@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions