From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org,
Arnd Bergmann <arnd@arndb.de>, Dmitry Mishin <dim@openvz.org>,
rusty@rustcorp.com.au, "David S. Miller" <davem@davemloft.net>,
devel@openvz.org
Subject: Re: [PATCH] iptables 32bit compat layer
Date: Wed, 29 Mar 2006 21:04:45 +0200 [thread overview]
Message-ID: <1143659085.4015.77.camel@localhost.localdomain> (raw)
In-Reply-To: <442A81DB.7060608@trash.net>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
On Wed, 2006-03-29 at 14:47 +0200, Patrick McHardy wrote:
> Dmitry Mishin wrote:
> > On Wednesday 29 March 2006 16:32, Patrick McHardy wrote:
> >>
> >>I know, but SOL_IPV6 implies IP6T_* - but please don't bother sending
> >>a new patch for this :) So the point of the change is to exclude IPv6
> >>from the compat layer because its not implemented yet?
> >
> > Exactly. Because do_netfilter_replace still works for some cases, but newer
> > replacement isn't ready yet.
>
> Ah OK. One last thing before I'll pass it on. There was one 64 bit
> architecture where iptables already worked with 32 bit userspace for
> some reason. I would like to make sure that it still works before it
> goes in because I can't debug it if it fails afterwards. I don't
> recall which arch it was, but I think Martin had one of these machines.
> Martin, could you give the compat patch a try?
It was an sparc64 machine with 32bit userspace I used for this testing.
Iirc, there was no problem adding/removing rules with the normal built
in matches and targets. The parts that were troublesome was some
matches/targets and rule counters.
That was worked around with very very very very ugly hacks in the
matches/targets in userspace, first an attempt to detect if we are
running 64/32 and if that's the case add some padding to some structs to
make the placement of used struct members match what's in kernel)
That machine (an old ultra1) hasn't seen electricity in a long time,
I'll see if I can dig it out this weekend unless someone else (dave?)
beats me to testing the patch.
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-29 19:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 8:10 [PATCH 1/2] iptables 32bit compat layer Mishin Dmitry
2006-02-20 8:14 ` [PATCH 2/2] " Mishin Dmitry
2006-02-20 8:31 ` [PATCH 1/2] " David S. Miller
2006-02-20 15:55 ` Arnd Bergmann
2006-02-21 9:04 ` [Devel] " Dmitry Mishin
2006-02-21 11:56 ` Arnd Bergmann
2006-03-07 14:07 ` {get|set}sockopt " Dmitry Mishin
2006-03-07 15:05 ` Arnd Bergmann
2006-03-09 10:23 ` Dmitry Mishin
2006-03-09 23:29 ` David S. Miller
2006-03-10 11:21 ` [PATCH] {get|set}sockopt compatibility layer Dmitry Mishin
2006-03-10 11:34 ` David S. Miller
2006-03-10 11:34 ` David S. Miller
2006-02-20 21:23 ` [PATCH 1/2] iptables 32bit compat layer Andi Kleen
2006-02-21 9:24 ` [Devel] " Dmitry Mishin
2006-03-23 10:24 ` [PATCH] " Dmitry Mishin
2006-03-29 9:28 ` Patrick McHardy
2006-03-29 11:36 ` Dmitry Mishin
2006-03-29 12:32 ` Patrick McHardy
2006-03-29 12:38 ` Dmitry Mishin
2006-03-29 12:47 ` Patrick McHardy
2006-03-29 19:04 ` Martin Josefsson [this message]
2006-03-29 21:53 ` David S. Miller
2006-03-29 23:01 ` Patrick McHardy
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=1143659085.4015.77.camel@localhost.localdomain \
--to=gandalf@wlug.westbo.se \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=dim@openvz.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
/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.