Revision d48102007d068df7ba3055cdc1723e12db1ba30f authored by Evgeniy Polyakov on 19 May 2005, 05:51:45 UTC, committed by David S. Miller on 19 May 2005, 05:51:45 UTC
It looks like skb_cow_data() does not set proper owner for newly created skb. If we have several fragments for skb and some of them are shared(?) or cloned (like in async IPsec) there might be a situation when we require recreating skb and thus using skb_copy() for it. Newly created skb has neither a destructor nor a socket assotiated with it, which must be copied from the old skb. As far as I can see, current code sets destructor and socket for the first one skb only and uses truesize of the first skb only to increment sk_wmem_alloc value. If above "analysis" is correct then attached patch fixes that. Signed-off-by: Evgeniy Polyakov <johnpol@2ka.mipt.ru> Acked-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent f7383c2
File | Mode | Size |
---|---|---|
Documentation | ||
arch | ||
crypto | ||
drivers | ||
fs | ||
include | ||
init | ||
ipc | ||
kernel | ||
lib | ||
mm | ||
net | ||
scripts | ||
security | ||
sound | ||
usr | ||
COPYING | -rw-r--r-- | 18.3 KB |
CREDITS | -rw-r--r-- | 87.1 KB |
MAINTAINERS | -rw-r--r-- | 55.8 KB |
Makefile | -rw-r--r-- | 43.2 KB |
README | -rw-r--r-- | 13.6 KB |
REPORTING-BUGS | -rw-r--r-- | 2.9 KB |
Computing file changes ...