Messages in this thread |  | | Date | Wed, 23 May 2001 16:55:57 +0200 | From | Andi Kleen <> | Subject | Re: sk_buff destructor in 2.2.18 |
| |
On Wed, May 23, 2001 at 04:50:28PM +0200, christophe barbé wrote: > I don't know about socket but I allocate myself the skbuff and I set the > destructor (and previously the pointer value is NULL). So I don't overwrite > a destructor.
That just means you didn't test all cases; e.g. not TCP or UDP send/receive.
> > I believe net/core/sock.c is not involved in my problem but I can be wrong. > What is worrying me is that I don't know who clones my skbuff and why.
skbuffs are cloned all over the stack for various reasons.
> To said everything, I know who clones my skbuff because it causes a oops > when it tries to free my buffer If I use my destructor.
Because you're mistakely using a private field.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |