[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <49E4744D.5090205@trash.net>
Date: Tue, 14 Apr 2009 13:32:29 +0200
From: Patrick McHardy <kaber@...sh.net>
To: Mariusz Kozlowski <m.kozlowski@...land.pl>
CC: Eric Dumazet <dada1@...mosbay.com>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Netfilter Development Mailinglist
<netfilter-devel@...r.kernel.org>,
Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: panic on rmmod of nf_conntrack_irc
Mariusz Kozlowski wrote:
> Recent kernels (i.e. 2.6.30-rc1) will panic while doing rmmod of nf_conntrack_irc.
>
> (gdb) l *(nf_conntrack_helper_unregister+0x158)
> 0x4f8 is in nf_conntrack_helper_unregister (/home/mako/linux/lkt/sources/linux-2.6/include/net/netfilter/nf_conntrack.h:133).
> 128 };
> 129
> 130 static inline struct nf_conn *
> 131 nf_ct_tuplehash_to_ctrack(const struct nf_conntrack_tuple_hash *hash)
> 132 {
> 133 return container_of(hash, struct nf_conn,
> 134 tuplehash[hash->tuple.dst.dir]);
> 135 }
> 136
> 137 static inline u_int16_t nf_ct_l3num(const struct nf_conn *ct)
>
>
> I bisected it down to
>
> netfilter: nf_conntrack: use SLAB_DESTROY_BY_RCU and get rid of call_rcu()
Thanks for the report. Does this patch fix it?
View attachment "x" of type "text/plain" (614 bytes)
Powered by blists - more mailing lists