Eric Dumazet c564039fd8 net: sk_wmem_alloc has initial value of one, not zero ... commit 2b85a34e91 (net: No more expensive sock_hold()/sock_put() on each tx) changed initial sk_wmem_alloc value. Some protocols check sk_wmem_alloc value to determine if a timer must delay socket deallocation. We must take care of the sk_wmem_alloc value being one instead of zero when no write allocations are pending. Reported by Ingo Molnar, and full diagnostic from David Miller. This patch introduces three helpers to get read/write allocations and a followup patch will use these helpers to report correct write allocations to user. Reported-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2009-06-17 04:31:25 -07:00
..
af_ax25.c	net: sk_wmem_alloc has initial value of one, not zero	2009-06-17 04:31:25 -07:00
ax25_addr.c
ax25_dev.c
ax25_ds_in.c
ax25_ds_subr.c
ax25_ds_timer.c
ax25_iface.c	ax25: more common return path joining	2009-02-06 23:47:14 -08:00
ax25_in.c
ax25_ip.c
ax25_out.c
ax25_route.c
ax25_std_in.c
ax25_std_subr.c
ax25_std_timer.c
ax25_subr.c
ax25_timer.c
ax25_uid.c	ax25: proc uid file misses header	2009-04-20 02:14:59 -07:00
Kconfig
Makefile
sysctl_net_ax25.c
TODO