All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kovacs Krisztian <piglet@sch.bme.hu>
To: netfilter-devel@lists.netfilter.org
Subject: Function pointers in conntrack structures
Date: Tue, 2 Sep 2003 15:16:16 +0200	[thread overview]
Message-ID: <20030902131616.GA3235@sch.bme.hu> (raw)


  Hi,

  I've found a weird looking function pointer in the connection tracking
system: the expectfn member of struct ip_conntrack_expect. AFAIK, this
function would be called by conntrack when a matching connection is found
for the registered expectation. However, I was unable to find any
conntrack helpers which use this functionality.

  My problem with this function pointer is that it cannot be replicated:
you cannot just send the function pointer over the wire, because on the
other nodes it may have completely different address. While there are
other pointers in the conntrack structures as well, all of them have some
kind of associated data which can be used as an ID. (For example: although
helpers -- which are function pointers of some kind -- are associated with
conntrack entries, however, they have to be registered, and the conntrack
entry is associated with the registered helper structure instead of just the
callback function. This is very important, because these structures all
contain a "name" field, which can be used as an ID.

  So, the only problem point I've found is the expectfn field of struct
ip_conntrack_expect, for which I've no idea how that could be handled. Is
the possibility of having more than one kind of callback function for
expectation creation really so important? (If only one kind of function
would be usable by conntrack helpers, its address could be stored in
struct ip_conntrack_helper, and we didn't have the whole problem.)

  Any ideas?

-- 
 Kovács Krisztián (Hidden)

             reply	other threads:[~2003-09-02 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 13:16 Kovacs Krisztian [this message]
2003-09-05 12:10 ` Function pointers in conntrack structures Harald Welte
2003-09-12 13:26   ` Jozsef Kadlecsik

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=20030902131616.GA3235@sch.bme.hu \
    --to=piglet@sch.bme.hu \
    --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.