02.03.2011, 17:37, "Changli Gao" <xiaosuo@xxxxxxxxx>: > t should be NULL here, as offsetof(struct nf_conn, dst.protonum) == 0x36. > We should free the nf_ct_extend with call_rcu(), since nat ext is > referenced in the rcu read context. Yes, I think the problem is triggered when nf_conntrack_free() is called by different CPU during net->ipv4.nat_bysource hash traversal. Extensions framework doesn't have any SLAB_DESTROY_BY_RCU magic. I'm not sure, but couldn't this problem be introduced by: ea781f197d6a835cbb93a0bf88ee1696296ed8aa netfilter: nf_conntrack: use SLAB_DESTROY_BY_RCU and get rid of call_rcu() ? -- wbr, Oleg. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
