From: Menyhart Zoltan <Zoltan.Menyhart@bull.net>
To: netfilter@vger.kernel.org
Subject: Cannot unload nf_conntrack
Date: Wed, 04 May 2011 11:08:38 +0200 [thread overview]
Message-ID: <4DC11796.4080702@bull.net> (raw)
Hi,
I cannot unload nf_conntrack because nf_conntrack_untracked.ct_general.use.counter == 7.
The last_unloaded_module is "nf_conntrack_ipv6".
Probably the following has happend:
nf_conntrack_in(struct net *net, u_int8_t pf, unsigned int hooknum, struct sk_buff *skb):
ret = l4proto->error(net, skb, dataoff, &ctinfo, pf, hooknum):
/* e.g. */ icmpv6_error(struct net *net, struct sk_buff *skb, unsigned int dataoff,
enum ip_conntrack_info *ctinfo, u_int8_t pf, unsigned int hooknum):
if (type >= 0 && type < sizeof(noct_valid_new) && noct_valid_new[type]) {
skb->nfct = &nf_conntrack_untracked.ct_general;
skb->nfctinfo = IP_CT_NEW;
nf_conntrack_get(skb->nfct);
return NF_ACCEPT;
}
ct = resolve_normal_ct(net, skb, dataoff, pf, protonum, l3proto, l4proto, &set_reply, &ctinfo);
skb->nfct = &ct->ct_general;
skb->nfctinfo = *ctinfo;
Is it normal for resolve_normal_ct() to overwrite skb->nfct without putting the previous conntrack?
It has actually happened on a 2.6.32, but the source is the same for 2.6.38, too.
A dump is available at ftp://visibull.frec.bull.fr/pub/linux/tmp.
Thanks in advance,
Zoltan Menyhart
reply other threads:[~2011-05-04 9:08 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=4DC11796.4080702@bull.net \
--to=zoltan.menyhart@bull.net \
--cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).