From: Eric Leblond <eric@regit.org>
To: James Morris <jmorris@intercode.com.au>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Libipq and invalid packet_id
Date: 26 Jun 2003 09:06:34 +0200 [thread overview]
Message-ID: <1056611194.32622.20.camel@porky> (raw)
In-Reply-To: <Mutt.LNX.4.44.0306261040110.11825-100000@excalibur.intercode.com.au>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
Le jeu 26/06/2003 à 02:40, James Morris a écrit :
> On 26 Jun 2003, Eric Leblond wrote:
> > - Is this a wanted feature ?
>
> No.
So I've got other related questions :
- How is memory managed, ie what's happen if we queue a lot of packet
without setting any verdict ?
- In particular, what's happened if we do successive call to
ipg_getmessage ? Do ipg_getmessage reuse address space after each call ?
BR,
--
Eric Leblond <eric@regit.org>
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-26 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 23:00 Libipq and invalid packet_id Eric Leblond
2003-06-26 0:40 ` James Morris
2003-06-26 7:06 ` Eric Leblond [this message]
2003-06-26 13:40 ` James Morris
2003-06-27 23:08 ` Eric Leblond
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=1056611194.32622.20.camel@porky \
--to=eric@regit.org \
--cc=jmorris@intercode.com.au \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.