All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Claessens <aaronc@eclipse-lighting.com>
To: netfilter-devel@lists.netfilter.org
Subject: ASSERT in ip_conntrack_core.c with PPTP helper
Date: Tue, 06 Apr 2004 17:26:22 -0500	[thread overview]
Message-ID: <40732E8E.8050003@eclipse-lighting.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
I believe that I have stumbled across a bug ....

I recieve when a PPTP session is started through the NAT interface:

Apr  6 16:44:48 NAT kernel: ASSERT ip_conntrack_core.c:93 
&ip_conntrack_lock_Rsmp_4193d6ac readlocked
Apr  6 16:44:48 NAT kernel: ASSERT ip_conntrack_core.c:1070 
&ip_conntrack_lock not readlocked
Apr  6 16:44:48 NAT kernel: ASSERT ip_nat_core.c:747 &ip_conntrack_lock 
not readlocked
Apr  6 16:44:48 NAT kernel: ASSERT ip_conntrack_core.c:80 
&ip_conntrack_lock not readlocked
Apr  6 16:44:48 NAT kernel: ASSERT ip_conntrack_core.c:82 
&ip_conntrack_lock not readlocked
Apr  6 16:44:48 NAT kernel: ASSERT ip_conntrack_core.c:1070 
&ip_conntrack_lock not readlocked
Apr  6 16:44:48 NAT kernel: ASSERT: ip_nat_core.c:850 &ip_conntrack_lock 
not readlocked

This was with:
iptables-1.2.9
linux-2.4.24 and 2.4.25

The following modules were loaded:
ipt_MASQUERADE
ipt_REJECT
ipt_LOG
ipt_limit
ipt_state
iptable_filter
ip_nat_pptp
ip_conntrack_pptp
ip_conntrack_proto_gre
iptable_nat
ip_tables
ip_conntrack

Let me know if I can provide more testing or information ....
Aaron


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAkBzLowACgkQiM4FRMeeny2hSACff4cjU0nnn/YW1PV4iBX1bYBN
yCkAoN3HY8jtiSt5+UzUem9zlo8ugRL6
=r3lP
-----END PGP SIGNATURE-----

                 reply	other threads:[~2004-04-06 22:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40732E8E.8050003@eclipse-lighting.com \
    --to=aaronc@eclipse-lighting.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.