From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Nielsen Subject: Re: Avoiding multiple calls to xt_target.checkentry Date: Wed, 03 Jun 2009 21:03:45 +1000 Message-ID: <4A265891.4050201@shikadi.net> References: <4A18A70F.50808@shikadi.net> <4A1DC798.1090604@shikadi.net> <4A26418C.5090707@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Jan Engelhardt , Netfilter Developer Mailing List To: Patrick McHardy Return-path: Received: from vitalin.sorra.shikadi.net ([64.71.152.201]:2858 "EHLO vitalin.sorra.shikadi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751484AbZFCLDv (ORCPT ); Wed, 3 Jun 2009 07:03:51 -0400 In-Reply-To: <4A26418C.5090707@trash.net> Sender: netfilter-devel-owner@vger.kernel.org List-ID: >> Thanks for the explanation! So - to get it straight in my mind - the >> checkentry function will be called multiple times while the trigger >> exists, >> but is the destroy function also called multiple times? Or is checkentry >> called whenever tables are created, but destroy only ever called once >> when the >> table is removed for the last time? > > They will always be called an equal amount of times - each one > once per target instance. Great, thanks for the info (thanks Jan too!) I'm working on a patch so I'll post it when I think I've solved the issue correctly. Cheers, Adam.