All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Valko <valko@linux.karinthy.hu>
To: "David S. Miller" <davem@redhat.com>
Cc: laforge@gnumonks.org, netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] sparc64 compatibility netfilter patches
Date: Thu, 2 Jan 2003 10:31:26 +0100	[thread overview]
Message-ID: <20030102103126.A32302@linux.karinthy.hu> (raw)
In-Reply-To: <20030102.010953.113716640.davem@redhat.com>; from davem@redhat.com on Thu, Jan 02, 2003 at 01:09:53AM -0800

On Thu, Jan 02, 2003 at 01:09:53AM -0800, David S. Miller wrote:
>    From: Harald Welte <laforge@gnumonks.org>
>    Date: Thu, 2 Jan 2003 09:57:34 +0100
> 
>    Unfortunately we will never get netfilter-specific code into the
>    sys_sparc32.c file (and we also really don't want it to be there).
>    
>    Is there no solution which only touches iptables userspace and kernel
>    code? (net/ipv4/netfilter/* as well as libiptc.c in userspace)?
>    
> It is the only way to translate socket options that include user
> pointers or other types that are not identical in the 32-bit
> and 64-bit environment.
> 
> It is always a bad idea to pass pointers and other non-hardcoded
> types (ie. something other than u8, u16 etc.) via APIs.

Either we change the way of data exchange, or we have to use similar
thunking functions. We could cosmetically beautify it by moving the
actual implementation from sys_sparc32.c into some other source file
(maybe net/ipv4/netfilter/nf_sparc32.c?) and call it from sys_sparc32.c,
this however provides only a maintenance ease. I see that this is
an important aspect, too.

Laszlo
e-mail: <valko@linux.karinthy.hu>

  reply	other threads:[~2003-01-02  9:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01 16:16 [PATCH] sparc64 compatibility netfilter patches Laszlo Valko
2003-01-01 20:32 ` Laszlo Valko
2003-01-02  6:22   ` David S. Miller
2003-01-02  9:20     ` Laszlo Valko
2003-01-07  8:47   ` David S. Miller
2003-01-02  8:57 ` Harald Welte
2003-01-02  9:09   ` David S. Miller
2003-01-02  9:31     ` Laszlo Valko [this message]
2003-01-02  9:41       ` David S. Miller

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=20030102103126.A32302@linux.karinthy.hu \
    --to=valko@linux.karinthy.hu \
    --cc=davem@redhat.com \
    --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.