All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [BUG?] ip6tables: 32bit userspace doesn't work with 64bit kernel
Date: Wed, 12 Dec 2007 09:36:52 +0100	[thread overview]
Message-ID: <475F9DA4.4000502@trash.net> (raw)
In-Reply-To: <68676e00712100509q1fcbf42dx6bcb46e95467ac91@mail.gmail.com>

Luca Tettamanti wrote:
> On Dec 9, 2007 5:13 PM, Patrick McHardy <kaber@trash.net> wrote:
>> Luca Tettamanti wrote:
>>> Hello,
>>> I just found out that 32bit (x86) ip6tables does not work with a 64bit
>>> kernel. I'm currenly using 2.6.24-rc4-g94545bad, but the structures
>>> involved haven't been touched recently.
>>>
>>> Before you read on: I see that IPv6 code is missing compat* stuff, so is
>>> this configuration supported?
>> Not yet, thanks for pointing this out, I completely forgot
>> about that :) I'll put it on my todo list, with some luck
>> I can still finish it in time for the 2.6.25 merge window.
> 
> Ok, feel free to throw patches this way for testing ;-)


I've completed the compat support, but its about 25 patches -
do you want me to start throwing? :) Otherwise just wait for
a few days, I'll send them upstream as soon as the iptables
compat fix is in net-2.6.25 since they depend on that one.




  reply	other threads:[~2007-12-12  8:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08 22:37 [BUG?] ip6tables: 32bit userspace doesn't work with 64bit kernel Luca Tettamanti
2007-12-09 16:13 ` Patrick McHardy
2007-12-10 13:09   ` Luca Tettamanti
2007-12-12  8:36     ` Patrick McHardy [this message]
2007-12-12 17:10       ` Patrick McHardy
2007-12-14 20:19         ` Luca Tettamanti

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=475F9DA4.4000502@trash.net \
    --to=kaber@trash.net \
    --cc=coreteam@netfilter.org \
    --cc=kronos.it@gmail.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.