All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Dibowitz <phil@ipom.com>
To: Phil Dibowitz <phil@ipom.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: libnetfilter_conntrack.h missing struct nf_conntrack definition
Date: Wed, 14 Mar 2007 22:25:40 -0700	[thread overview]
Message-ID: <45F8D8D4.7000909@ipom.com> (raw)
In-Reply-To: <20070314222130.GB31683@ipom.com>

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

Phil Dibowitz wrote:
> None of the libnetfilter_conntrack's "public" headers include the full
> definition of struct nf_conntrack.
> 
> It's not a 'private' structure (__*), thought it uses private structures
> within it...  This means I can't do things like memcpy() them, sizeof() them,
> or even build an STL vector of them (yeah, I know, ew, yuck, c++).
> 
> Since nf_conntrack structs are passed around to the applications using nfct,
> it seems reasonable to desire to do things with them.

Looks like this was sorta thought of. Apparently you can return
NFCT_CB_STOLEN which will cause it to not be freed. I can then keep pointers
to the object rather than the object itself...

Oh well - I already restructured my code to get around this. :)

So you can ignore the original email.

-- 
Phil Dibowitz                             phil@ipom.com
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Never write it in C if you can do it in 'awk';
 Never do it in 'awk' if 'sed' can handle it;
 Never use 'sed' when 'tr' can do the job;
 Never invoke 'tr' when 'cat' is sufficient;
 Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      reply	other threads:[~2007-03-15  5:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 22:21 libnetfilter_conntrack.h missing struct nf_conntrack definition Phil Dibowitz
2007-03-15  5:25 ` Phil Dibowitz [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=45F8D8D4.7000909@ipom.com \
    --to=phil@ipom.com \
    --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.