From: Nicolas Dichtel <nicolas.dichtel@dev.6wind.com>
To: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: 32 vs 64 bits
Date: Thu, 26 Mar 2009 15:26:01 +0100 [thread overview]
Message-ID: <49CB9079.9070309@dev.6wind.com> (raw)
Hi all,
I'm trying to understand why the following commit has been done:
http://git.netfilter.org/cgi-bin/gitweb.cgi?p=iptables.git;a=commitdiff;h=7d5cc229064b0e718046b9ecaebad3426dfff15f
Removes KERNEL_64_USERSPACE_32
Yasuyuki KOZAKAI [Sat, 30 Jun 2007 10:47:57 +0000 (10:47 +0000)]
The recent kernel has compat layer for iptables. It doesn't have
compat layer for libipq and ip6tables, but ip6tables with
KERNEL_64_USERSPACE_32 is still broken. We should fix kernel instead of
fixing them if and when we want use their 32bit binary with 64bit kernel.
Where is the compat layer? If I look in a recent kernel, it seems that
ip_queue.h still uses long and is broken.
http://git.kernel.org/?p=linux/kernel/git/davem/net-next-2.6.git;a=blob;f=include/linux/netfilter_ipv4/ip_queue.h;hb=59b8bfd8fd608821e5addc9f4682c7f2424afd8c
Am I wrong?
If yes, what is the right way to fix this? Updating the API?
Thank you,
Nicolas
next reply other threads:[~2009-03-26 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 14:26 Nicolas Dichtel [this message]
2009-03-26 14:32 ` 32 vs 64 bits Jan Engelhardt
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=49CB9079.9070309@dev.6wind.com \
--to=nicolas.dichtel@dev.6wind.com \
--cc=netfilter-devel@vger.kernel.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.