checkentry() and detroy () called multiple times

checkentry() and detroy () called multiple times

[diegows]

I 'm doing a match module and I have i little confusion.

If I insert a rule using my match module, I see that checkentry() is 
called once. If I insert a rule using my match module again I see that 
checkentry() is called twice and destroy is called once, and If i insert 
a rule for third time I see that checkentry is called tree times and 
destroy twice.

Is this the right? why?

Re: checkentry() and detroy () called multiple times

[Harald Welte]

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Mon, May 12, 2003 at 11:22:00AM -0300, diegows wrote:
> I 'm doing a match module and I have i little confusion.
> 
> If I insert a rule using my match module, I see that checkentry() is 
> called once. If I insert a rule using my match module again I see that 
> checkentry() is called twice and destroy is called once, and If i insert 
> a rule for third time I see that checkentry is called tree times and 
> destroy twice.

because checkentry is called for every rule that is using your match in
this table.  It is supposed to check the *matchinfo data passed on from
userspace.

> Is this the right? why?

yes. see above.

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]