All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Andrew Morton <akpm@osdl.org>
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org, mroos@linux.ee
Subject: Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)
Date: Thu, 25 May 2006 20:52:44 +0200	[thread overview]
Message-ID: <4475FCFC.5000701@trash.net> (raw)
In-Reply-To: <20060525070324.2ea16b0a.akpm@osdl.org>

Andrew Morton wrote:
> bugme-daemon@bugzilla.kernel.org wrote:
> 
>>http://bugzilla.kernel.org/show_bug.cgi?id=6613
>>
>>           Summary: iptables broken on 32-bit PReP (ARCH=ppc)
>>    Kernel Version: 2.6.17-rc4
>>            Status: NEW
>>          Severity: normal
>>             Owner: laforge@gnumonks.org
>>         Submitter: mroos@linux.ee
>>
>>
>>Most recent kernel where this bug did not occur: none known, this is a fresh 
>>install
>>Distribution: Debian unstable
>>Hardware Environment: 32-bit PowerPC 604 with PReP subarch (using old 
>>ARCH=ppc)
>>Software Environment: usual 32-bit ppc userspace, gcc 4.0.3
>>Problem Description: iptables operations usually just give "Incalida 
>>operation". modprobe iptable_filter and adding rules to the nat table have 
>>failed in testing while iptable_nat can be modprobed and listed.
>>
>>Steps to reproduce:
>>modprobe iptable_filter (errors out with Invalid Argument)
>>iptables -t nat -A POSTROUTING -s 10.0.0.0/8 -j SNAT --to 192.168.1.1 (usually 
>>errors out with Invalid Argument, sometimes succeeds, when succeeds then the 
>>rule works fine)


Meelis, it would really help if you could try 2.6.16 and in case
that doesn't work 2.6.15 to give an idea about whether this is a
recent regression or an old problem. We had a number of changes
in this area in the last two kernel versions that could be related.


  reply	other threads:[~2006-05-25 18:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605251004.k4PA4Lek007751@fire-2.osdl.org>
2006-05-25 14:03 ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Andrew Morton
2006-05-25 18:52   ` Patrick McHardy [this message]
2006-05-25 19:12     ` Meelis Roos
2006-05-25 20:15     ` Meelis Roos
2006-05-26  7:11     ` Meelis Roos
2006-05-26 12:29       ` Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)) Ingo Oeser
2006-05-26 12:34         ` Meelis Roos
2006-05-31 20:25           ` Bill Davidsen
2006-05-26 12:42         ` Michael Tokarev
2006-05-26 12:42         ` Andi Kleen
2006-05-26 13:21           ` Ingo Oeser
2006-06-01  7:03     ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Meelis Roos
2006-06-01 17:44       ` Patrick McHardy
2006-06-01 20:50         ` Meelis Roos
2006-06-02 13:08           ` Patrick McHardy
2006-06-02 13:18             ` Meelis Roos
2006-06-02 13:56               ` Patrick McHardy
2006-06-04 12:39                 ` Meelis Roos

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=4475FCFC.5000701@trash.net \
    --to=kaber@trash.net \
    --cc=akpm@osdl.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=mroos@linux.ee \
    --cc=netdev@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.