diff options
| author | Eric Dumazet <edumazet@google.com> | 2014-04-03 09:28:10 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-06-07 16:02:00 -0700 |
| commit | d16beab575e17e46a4b187fb9f8211fab3adfbae (patch) | |
| tree | 03d690603fd7481aa2c01373cd95562bf69e371d /kernel | |
| parent | 1102122b2bdf4307cae269c725fab4c9c6141f5b (diff) | |
| download | lwn-d16beab575e17e46a4b187fb9f8211fab3adfbae.tar.gz lwn-d16beab575e17e46a4b187fb9f8211fab3adfbae.zip | |
net-gro: reset skb->truesize in napi_reuse_skb()
[ Upstream commit e33d0ba8047b049c9262fdb1fcafb93cb52ceceb ]
Recycling skb always had been very tough...
This time it appears GRO layer can accumulate skb->truesize
adjustments made by drivers when they attach a fragment to skb.
skb_gro_receive() can only subtract from skb->truesize the used part
of a fragment.
I spotted this problem seeing TcpExtPruneCalled and
TcpExtTCPRcvCollapsed that were unexpected with a recent kernel, where
TCP receive window should be sized properly to accept traffic coming
from a driver not overshooting skb->truesize.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions