From: Laszlo Valko <valko@linux.karinthy.hu>
To: Thomas Heinz <creatix@hipac.org>
Cc: Anders Fugmann <afu@fugmann.dhs.org>,
netfilter-devel@lists.netfilter.org
Subject: Re: Comments about IPT_ALIGN
Date: Sun, 26 Jan 2003 20:31:12 +0100 [thread overview]
Message-ID: <20030126203112.A9418@linux.karinthy.hu> (raw)
In-Reply-To: <3E3411CD.3050603@hipac.org>; from creatix@hipac.org on Sun, Jan 26, 2003 at 05:50:21PM +0100
Hi Thomas!
On Sun, Jan 26, 2003 at 05:50:21PM +0100, Thomas Heinz wrote:
> > Yes, that's true, except for the fact that you will have to deal
> > with endianness as well, if you are interested in actually exchanging
> > data...
>
> The only match/target I'm aware of that has a pointer in its info
> struct is the limit match. Generally this is necessary for each
There's one in struct ipt_replace (indeed that's not a match/target),
for the counters.
> match/target that does not treat the info data as read only on a
> smp system (at least with the current infrastructure as each cpu has
> its own match/target info).
>
> Anyway, I don't see a reason why one wants to exchange a valid pointer
> between user and kernel space.
I have seen at least two guys here who asked how to exchange arbitrary
amount of data. And a pointer is an easy way out...
> > And don't forget the size change that brings in on every 32-bit
> > platform effectively killing compatibility...
>
> One could use #ifdef's for compatibility purpose but as I read you
> don't like these :-)
I could put up with that one :) But I doubt that we could get that "solution"
accepted into mainline releases...
Regards,
Laszlo
>
>
> Thomas
>
next prev parent reply other threads:[~2003-01-26 19:31 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 [this message]
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
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=20030126203112.A9418@linux.karinthy.hu \
--to=valko@linux.karinthy.hu \
--cc=afu@fugmann.dhs.org \
--cc=creatix@hipac.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.