Messages in this thread | | | Date | Wed, 23 May 2001 16:50:28 +0200 | From | christophe barbé <> | Subject | Re: sk_buff destructor in 2.2.18 |
| |
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.
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.
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.
Christophe
On Wed, 23 May 2001 16:40:36 Andi Kleen wrote: > On Wed, May 23, 2001 at 04:37:58PM +0200, christophe barbé wrote: > > It seems to not be the case, because my destructor is called. > > It is called, but you overwrote the kernel destructor and therefore > broke the socket memory accounting completely; causing all kinds of > problems. > > > Could you point me the code where you think this method is already > used? > > net/core/sock.c > > > -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/ > -- Christophe Barbé Software Engineer - christophe.barbe@lineo.fr Lineo France - Lineo High Availability Group 42-46, rue Médéric - 92110 Clichy - France phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01 http://www.lineo.com
- 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/
| |