All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: sparc64 match module - bug id 94
Date: Sun, 09 May 2004 16:30:34 +0200	[thread overview]
Message-ID: <409E408A.7060608@eurodev.net> (raw)
In-Reply-To: <20040505065402.GA18440@hamachi.radom.org>

Hi,

I think that if we use the autoconf stuff in iptables (see "[PATCH] 
Autoconf stuff for iptables"), we can workaround this problem by 
defining a different ipt_limit.h header in the iptables tree, actually a 
not so different header, just the same ipt_limit.h file but it contains 
in this case:

#ifdef __sparc64__
    u_int64_t master;
#else
    struct ipt_rateinfo *master;
#endif

so we shouldn't need to modify anything in kernel. This way we can keep 
those ifdef's in user space to workaround problems with tricky 
architectures which have different types in kernel and user space. Well, 
it's not so clean but it's easy.

regards,
Pablo

  parent reply	other threads:[~2004-05-09 14:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05  6:54 sparc64 match module - bug id 94 dan radom
2004-05-06 10:12 ` Henrik Nordstrom
2004-05-06 14:09   ` KOVACS Krisztian
2004-05-06 14:56     ` Pablo Neira
2004-05-07  6:30       ` Henrik Nordstrom
2004-05-06 15:33     ` Jozsef Kadlecsik
2004-05-07  6:20       ` Henrik Nordstrom
2004-05-06 14:29 ` Pablo Neira
2004-05-06 14:47   ` Chris Wilson
2004-05-06 14:39     ` Pablo Neira
2004-05-09 14:30 ` Pablo Neira [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-04 12:14 dan radom
2004-05-04 14:32 ` Antony Stone

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=409E408A.7060608@eurodev.net \
    --to=pablo@eurodev.net \
    --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.