All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Greg Scott <GregScott@InfraSupportEtc.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227
Date: Tue, 03 Jan 2006 13:10:58 +0100	[thread overview]
Message-ID: <43BA69D2.8020703@trash.net> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A26D46@mail733.InfraSupportEtc.com>

Greg Scott wrote:
> Yup, the h323 modules are broken.  The h323 modules reference a function
> named ip_conntrack_expect_free.  But searching through the entire kernel
> and POM source trees, I find no reference to any files named similarly.
> And searching through the netfilter-devel archives from Dec. 2005
> through June 2005, I find no mention of this string.  Have I hit a brick
> wall or can I remove the references to this function in the effected
> h323 modules?  If yes, I will even try my hand at making a patch.

Expectations are now reference counted, which means you need to
use ip_conntrack_expect_put(). Beware that the semantic has changed,
you need to put every expectation, independant of the success of
ip_conntrack_expect_register(). IIRC the H323 helper has a few other
critical problems, it doesn't set expectfn to NULL in the H.245 helper
(which crashes when the NAT helper is not loaded) and also doesn't
initialize the flags member in the expectation (needs to be 0).

I have a majorly reworked version for some older kernel, it doesn't
compile currently, but I plan to continue working on it in the
near future.

  reply	other threads:[~2006-01-03 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-29 16:04 Kernel build suspicious warnings 2.6.14-5, iptables 1.3.4, POM-20051227 Greg Scott
2006-01-03 12:10 ` Patrick McHardy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-29 15:05 Greg Scott
2005-12-29 13:48 Greg Scott
2005-12-29  6:44 Greg Scott
2005-12-29 10:30 ` David S. Miller

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=43BA69D2.8020703@trash.net \
    --to=kaber@trash.net \
    --cc=GregScott@InfraSupportEtc.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.