RE: ip_conntrack_lock not readlocked ? anyone ....

hello -

Please do not post html to this mailing list. Antony. -- What is this talk of software 'release' ? Our software evolves and matures until it becomes capable of escape, leaving a bloody trail of designers and quality assurance people in its wake. From mboxrd@z Thu Jan 1 00:00:00 1970 From: "hallian hallian" Subject: ip_conntrack_lock not readlocked? anyone? Date: Wed, 16 Oct 2002 16:18:49 -0400 Sender: netfilter-admin@lists.netfilter.org Message-ID: Mime-Version: 1.0 Return-path: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: netfilter@lists.netfilter.org

hello -

I was wondering if anyone has seen this er= ror/warning message before? What does it mean? Any idea?

regards,

hallian

=3D=3D=3D

Oct 13 11:50:18 f kernel: ASSERT ip_nat_co= re.c:739 &ip_conntrack_lock_Rsmp_4193d6ac readlocked
Oct 13 11:50:18= f kernel: ASSERT ip_conntrack_core.c:91 &ip_conntrack_lock_Rsmp_4193d6= ac readlocked
Oct 13 11:50:18 f kernel: ASSERT: ip_nat_core.c:743 &i= p_conntrack_lock not readlocked
Oct 13 11:50:18 f kernel: ASSERT ip_conn= track_core.c:977 &ip_conntrack_lock not readlocked
Oct 13 11:50:18 f= kernel: ASSERT: ip_nat_core.c:840 &ip_conntrack_lock not readlockedOct 13 11:50:18 f kernel: ASSERT ip_nat_core.c:739 &ip_conntrack_lock_= Rsmp_4193d6ac readlocked
Oct 13 11:50:18 f kernel: ASSERT ip_conntrack_c= ore.c:91 &ip_conntrack_lock_Rsmp_4193d6ac readlocked
Oct 13 11:50:18= f kernel: ASSERT: ip_nat_core.c:743 &ip_conntrack_lock not readlocked<= BR>Oct 13 11:50:18 f kernel: ASSERT: ip_nat_core.c:840 &ip_conntrack_lo= ck not readlocked

Hi,

smalik@vistawiz.com [mailto:smalik@vistawiz.com] = wrote:
>hello everyone -
>
>I was wondering if someone has seen this error message before. = Prt what
>does is mean? I am running iptables 1.2.7.
>
>Oct 13 11:50:18 fire kernel: ASSERT ip_nat_core.c:739
>&ip_conntrack_lock_Rsmp_4193d6ac readlocked
>Oct 13 11:50:18 fire kernel: ASSERT ip_conntrack_core.c:91
>&ip_conntrack_lock_Rsmp_4193d6ac readlocked
>Oct 13 11:50:18 fire kernel: ASSERT: ip_nat_core.c:743 = &ip_conntrack_lock
>not readlocked
>Oct 13 11:50:18 fire kernel: ASSERT ip_conntrack_core.c:977
>&ip_conntrack_lock not readlocked
>Oct 13 11:50:18 fire kernel: ASSERT: ip_nat_core.c:840 = &ip_conntrack_lock
>not readlocked
>Oct 13 11:50:18 fire kernel: ASSERT ip_nat_core.c:739
>&ip_conntrack_lock_Rsmp_4193d6ac readlocked
>Oct 13 11:50:18 fire kernel: ASSERT ip_conntrack_core.c:91
>&ip_conntrack_lock_Rsmp_4193d6ac readlocked
>Oct 13 11:50:18 fire kernel: ASSERT: ip_nat_core.c:743 = &ip_conntrack_lock
>not readlocked
>Oct 13 11:50:18 firekernel: ASSERT: ip_nat_core.c:840 = &ip_conntrack_lock
>not readlocked
>

Is that on a kernel with newnat, like 2.4.20-pre something ?

It's harmless but annoying - check the archives of netfilter-devel
for the discussion and fix by Martin Josefsson. That fix is already
in 2.4.20-pre11.

Regards,
Filip

------_=_NextPart_001_01C2756D.B3702934--