2.0.3x skb leak

Philip Gladstone (philip@raptor.com)
Fri, 12 Jun 1998 14:33:48 -0400

It seems that if an skb gets into the free=3 state (i.e. it was
freed while locked), then it never gets freed later. In
particular, skb_device_unlock does not try and free the skb.

However, the fix is not obvious -- should I call
kfree_skb(, FREE_WRITE) at the end of skb_device_unlock or
FREE_READ, or should the read/write flag be maintained in the
skb.

This is not an abstract problem -- I have a bit of code that
can use up all of kernel memory in a few seconds.

Philip

-- 
Philip Gladstone                           +1 781 530 2461
Raptor Systems / Axent Technologies 
Waltham, MA         		    http://www.raptor.com/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu