linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: dev@openvz.org
Cc: linux-kernel@vger.kernel.org, dim@openvz.org,
	netfilter-devel@lists.netfilter.org, rusty@rustcorp.com.au,
	akpm@osdl.org
Subject: Re: [RFC][DRAFT][PATCH] iptables 32bit compat layer
Date: Wed, 18 Jan 2006 01:38:41 -0800 (PST)	[thread overview]
Message-ID: <20060118.013841.123630757.davem@davemloft.net> (raw)
In-Reply-To: <43CE0696.50407@openvz.org>

From: Kirill Korotaev <dev@openvz.org>
Date: Wed, 18 Jan 2006 12:12:54 +0300

> This patch extends current iptables compatibility layer in order to get
> 32bit iptables to work on 64bit kernel. Current layer is insufficient 
> due to alignment checks both in kernel and user space tools. Current 
> draft version works correctly with standard targets only 
> (ACCEPT/DROP/FORWARD).
> 
> ToDo:
>   - extend translation to include more matches and targets. Use arrays of
>     structures like { name, size_diff, func_for_convert_data} for this
>     purpose
>   - extend get_info to return corrected size. Add size calculation to
>     get_entries.

Thanks for doing this work.

But it would make a lot more sense to add
compat_setsockopt and compat_getsockopt socket
operations, call down into there, and then implement
these translations inside of netfilter itself.

This would avoid an enormous amount of copying
and munging, and also would keep netfilter internals
outside of the generic socket compat layer code.

Thanks.

      reply	other threads:[~2006-01-18  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18  9:12 [RFC][DRAFT][PATCH] iptables 32bit compat layer Kirill Korotaev
2006-01-18  9:38 ` David S. Miller [this message]

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=20060118.013841.123630757.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@osdl.org \
    --cc=dev@openvz.org \
    --cc=dim@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).