From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Subject: Re: sparc64 match module - bug id 94 Date: Thu, 06 May 2004 16:56:28 +0200 Sender: netfilter-devel-admin@lists.netfilter.org Message-ID: <409A521C.5020406@eurodev.net> References: <1083852576.1822.18.camel@nienna.balabit> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: To: KOVACS Krisztian , Netfilter Development Mailinglist In-Reply-To: <1083852576.1822.18.camel@nienna.balabit> Errors-To: netfilter-devel-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: netfilter-devel.vger.kernel.org Hi Krisztian, KOVACS Krisztian wrote: > A possible hack: let's define two separate structures, one for >in-kernel use, and one for the userspace. > > I thought about that possibility, it's an interesting hack, but I think that the problem is much more specific, we have only this problem with ipt_limit. Actually, when we have some internal match information which is shared by some processors, we need to know which one is the selected to work with. So, we could add a pointer to the master of internal match data in struct ipt_entry_match. what do you think? regards, Pablo