From: Laszlo Valko <valko@linux.karinthy.hu>
To: Harald Welte <laforge@gnumonks.org>
Cc: Anders Fugmann <afu@fugmann.dhs.org>,
Thomas Heinz <creatix@hipac.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: Comments about IPT_ALIGN
Date: Sat, 1 Feb 2003 00:37:50 +0100 [thread overview]
Message-ID: <20030201003750.A27624@linux.karinthy.hu> (raw)
In-Reply-To: <20030131115512.GW9073@naboo.cybercafe42>; from laforge@gnumonks.org on Fri, Jan 31, 2003 at 12:55:12PM +0100
Hi Harald!
On Fri, Jan 31, 2003 at 12:55:12PM +0100, Harald Welte wrote:
> On Sun, Jan 26, 2003 at 03:22:27PM +0100, Laszlo Valko wrote:
> > Currently, I see two ways:
> > 1) make a translation function for all currently existing netfilter structures
> > that use longs or pointers (difficult, as modules can be added
> > independently), like those in arch/sparc64/sys_sparc32.c, and its
> > friends,
>
> it's a hack, but it would work.
Well, we will definitely need it if people want to use netfilter on 2.4,
as that is a stable series, and we don't want to introduce incompatibilities
I guess.
When I arrive to the state of having a little spare time, I might convince
myself to sketch a first version up... It does not look too difficult at least.
> > 2) introduce a new way of passing structures, with new structures, probably
> > with new setsockopt/getsockopt numbers, essentially creating an API
> > incompatible with the existing one (there are a few other bleeding wounds
> > waiting to be solved in the existing interface as I saw).
>
> please don't go for solution #2. There is already one new interface
> between kernel an userspace in development... we don't need more
> interfaces than we already have.
Wow! May I see it? :)
> And yes, the new interface still has the matchinfo of all matches
> concatenated in one memory area. Everything else has linked lists,
> though (e.g. every rule is a seperately allocated memory chunk).
That's all right, as long as the interface structures != kernel internal
structures. In fact kernel internal structure should be >= interface structure.
Otherwise you cannot solve the problem of using unsigned longs in
interface structures (eg jiffies is always unsigned long unfortunately).
Do we expect to change the modules as well? I mean struct ipt_anything et al.
are expected to change, is that so?
Regards,
Laszlo
>
> --
> Live long and prosper
> - Harald Welte / laforge@gnumonks.org http://www.gnumonks.org/
> ============================================================================
> GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
> V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
next prev parent reply other threads:[~2003-01-31 23:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 3:57 Comments about IPT_ALIGN Thomas Heinz
2003-01-26 11:01 ` Laszlo Valko
2003-01-26 11:28 ` Anders Fugmann
2003-01-26 13:58 ` Thomas Heinz
2003-01-26 14:26 ` Laszlo Valko
2003-01-26 16:50 ` Thomas Heinz
2003-01-26 19:31 ` Laszlo Valko
2003-01-31 11:51 ` Harald Welte
2003-01-26 14:22 ` Laszlo Valko
2003-01-26 18:05 ` Thomas Heinz
2003-01-26 19:43 ` Laszlo Valko
2003-01-26 23:09 ` Thomas Heinz
2003-01-27 0:43 ` Laszlo Valko
2003-01-27 10:33 ` Thomas Heinz
2003-01-31 11:57 ` Harald Welte
2003-01-26 19:48 ` Thomas Heinz
2003-01-31 11:55 ` Harald Welte
2003-01-31 23:37 ` Laszlo Valko [this message]
2003-01-26 17:06 ` Thomas Heinz
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=20030201003750.A27624@linux.karinthy.hu \
--to=valko@linux.karinthy.hu \
--cc=afu@fugmann.dhs.org \
--cc=creatix@hipac.org \
--cc=laforge@gnumonks.org \
--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.