On Thu, Aug 06, 2015 at 03:44:47PM +0200, Andreas Schultz wrote: > On 08/06/2015 03:42 PM, Pablo Neira Ayuso wrote: [...] > >With netns in place, we don't know in what order the __net_exit > >functions are called, ie. We may still have references to objects from > >xt_nfacct. > > Exactly my point, only the xt_nfacct object references also takes a > module reference. We can not release this reference for them. So > we remove the nfacct object from the list and only free the object > if xt_nfacct is *NOT* holding a reference. > > If xt_nfacct is holding a reference, it will put that reference together > with the module reference later. You're right. This patch is applied, thanks Andreas: BTW, I have mangled the original subject to: netfilter: nfacct: per network namespace support Just for the next time, we prefer this format: SUBSYS: COMPONENT: description -- 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
