public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Duncan Sands <baldrick@free.fr>
To: emmanuel@netlab.hut.fi, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Freeing skbuff (was: Re: Sending built-by-hand packet and kernel panic.)
Date: Wed, 4 Feb 2004 11:27:45 +0100	[thread overview]
Message-ID: <200402041127.45346.baldrick@free.fr> (raw)
In-Reply-To: <401E8E33.7050305@netlab.hut.fi>

> Thanks a lot for pointing out these problems. I had completely missed them.
> However, my overall problem is not solved. As far as my investigations
> led me, my sk_buff structure is never released after having been sent on
> the wire. So I guess I need an explicit destructor function in my
> sk_buff as the following is present in the definition of struct sk_buff:
> void         (*destructor)(struct sk_buff *);    /* Destruct function
>     */

Hi Emmanuel, maybe the call that sends to skb (NF_HOOK) is returning
a non-zero error code.  In that case it is your responsability [1] to free the
skb.

Duncan.

[1] This is true for many parts of the kernel but not all.  I don't know what
NF_HOOK is so this may not apply here.

      parent reply	other threads:[~2004-02-04 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 14:46 Sending built-by-hand packet and kernel panic Emmanuel Guiton
     [not found] ` <200402021602.56242.baldrick@free.fr>
2004-02-02 17:51   ` Freeing skbuff (was: Re: Sending built-by-hand packet and kernel panic.) Emmanuel Guiton
2004-02-03  9:49     ` Muli Ben-Yehuda
2004-02-06  6:58       ` Emmanuel Guiton
2004-02-04 10:27     ` Duncan Sands [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200402041127.45346.baldrick@free.fr \
    --to=baldrick@free.fr \
    --cc=emmanuel@netlab.hut.fi \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox