diff options
| author | Eric Dumazet <edumazet@google.com> | 2014-04-03 09:28:10 -0700 |
|---|---|---|
| committer | Jiri Slaby <jslaby@suse.cz> | 2014-05-29 11:49:34 +0200 |
| commit | ac993cf25a957b332864e3200644b50e179826fc (patch) | |
| tree | 9351915f448fe00a5e6e7acb599ae697d1d41b69 /crypto/testmgr.c | |
| parent | ee08bba5f0f2c32f12a465542ad4b6a42c4a1417 (diff) | |
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: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'crypto/testmgr.c')
0 files changed, 0 insertions, 0 deletions