re &ip_conntrack_lock not readlocked
I have been seeing the message
=======================
Nov 12 09:58:01 clients kernel: ASSERT: ip_nat_core.c:839 &ip_conntrack_lock not readlocked Nov 12 09:58:01 clients kernel: ASSERT ip_conntrack_core.c:94 &ip_conntrack_lock_Rsmp_4193d6ac readlocked Nov 12 09:58:01 clients kernel: ASSERT: ip_nat_core.c:839 &ip_conntrack_lock
not readlocked
=======================
in the logs and believe it may be related to having aliases on the card eg eth0:1 etc
This is with kernel 2.4.18 and iptables-1.2.7a
I'm not sure that it's actually doing any harm but can not find much about it.
any helpful comments would be apreciated
Kind Regards
Simon May
Network Administrator
Internet Marketing S.L.
Telephone 971 72 92 04
Fax 971 71 92 04
Email [email protected]
Quoted 9 lines · Simon May
I have been seeing the message
Nov 12 09:58:01 clients kernel: ASSERT: ip_nat_core.c:839 &ip_conntrack_locknot readlocked
in the logs and believe it may be related toI'm not sure that it's actually doing any harm but can not find much about it.
any helpful comments would be apreciated
please read the list archives. It's a problem in the debug statement, not the code itself.
Quoted 1 line
Simon May
Signature · 5 lines
Live long and prosper - Harald Welte / [email protected] http://www.gnumonks.org/ ============================================================================ GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M- V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)