Hello,
since I yesterday upgraded kernel on my box at home, it keeps dying in few minutes due to deadlock in destroy_conntrack, acquiring ip_conntrack_lock which was already acquired by ip_ct_refresh_acct. Box setup is quite simple: there are no iptable rules, just ip_conntrack is loaded, but should do nothing.

  Host is UP x86_64 box running SMP kernel, NIC in use sk98lin.  Callstack is:

_write_lock_irqsave+60
_write_lock_bh+6
:ip_conntrack:destroy_conntrack+114 << this wants it too as refcount hit zero...
:ip_conntrack:__ip_ct_event_cache_init+144
:ip_conntrack:ip_ct_refresh_acct+203<< this acquired ip_conntrack_lock
:ip_conntrack:udp_packet+47
:ip_conntrack:ip_conntrack_in+575
nf_iterate+94
nf_hook_slow+135
ip_push_pending_frames+890
udp_push_pending_frames+551
udp_sendmsg+1619
inet_sendmsg+83
sock_sendmsg+238
sys_sendto+...
compat_socketcall+...
ia32_sysret+0

and it is always triggered by nscd, probably when it sends out DNS query and is unlucky. Problem did not exist in plain 2.6.13.
                                        Thanks,
                                                Petr Vandrovec


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to