All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: KOVACS Krisztian <hidden@balabit.hu>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: sparc64 match module - bug id 94
Date: Thu, 06 May 2004 16:56:28 +0200	[thread overview]
Message-ID: <409A521C.5020406@eurodev.net> (raw)
In-Reply-To: <1083852576.1822.18.camel@nienna.balabit>

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

  reply	other threads:[~2004-05-06 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05  6:54 sparc64 match module - bug id 94 dan radom
2004-05-06 10:12 ` Henrik Nordstrom
2004-05-06 14:09   ` KOVACS Krisztian
2004-05-06 14:56     ` Pablo Neira [this message]
2004-05-07  6:30       ` Henrik Nordstrom
2004-05-06 15:33     ` Jozsef Kadlecsik
2004-05-07  6:20       ` Henrik Nordstrom
2004-05-06 14:29 ` Pablo Neira
2004-05-06 14:47   ` Chris Wilson
2004-05-06 14:39     ` Pablo Neira
2004-05-09 14:30 ` Pablo Neira
  -- strict thread matches above, loose matches on Subject: below --
2004-05-04 12:14 dan radom
2004-05-04 14:32 ` Antony Stone

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=409A521C.5020406@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=hidden@balabit.hu \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.