Re: iptables broken on ppc (ptrace too?) (2.6.17-rc3)
32-bit kernel, this is a Motorola Powerstack II macine with 604e. PReP subarch, only buildable from the old ARCH=ppc code (not yet migrated to ARCH=powerpc). Ah OK, I thought it was related to the new compat code, but that isn't the case. Your trace doesn't give much clues, except that it shows that iptables dies with a SIGSEGV, which might be a bug in userspace or in the kernel. Which was the last kernel that worked for you, and can you try that version again to rule out userspace bugs? Even worse. With yesterdays git iptable_nat loads but iptable_filter doesn't even load (Invalid argument). -- Meelis Roos ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: iptables broken on ppc (ptrace too?) (2.6.17-rc3)
Iptables seems to be broken on ppc for me. Kernel 2.6.17-rc3 (currently compiling rc4+git). 32-bit ppc, ARCH=ppc with PReP target. Iptables userland binary is from the latest Debian unstable (1.3.3-2). The symptoms: iptables usually just tells Invalid Argument on any modification attempt. I'm trying to set up a simple one-rule NAT for test: iptables -t nat -A POSTROUTING -s 172.30.0.0/24 -j SNAT --to 10.0.0.1 and it usually fails but has succeeded 2 times (I now have 2 rules of this kind and they seem to just wotk once set up). Trying to delete the second rule (either by replacing -A with -D or using just -D 2) gives the same error. This should already be fixed in -rc4. Unfortunately it was still there with yesterdays rc4+git. -- Meelis Roos ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: iptables broken on ppc (ptrace too?) (2.6.17-rc3)
Meelis Roos wrote: Iptables seems to be broken on ppc for me. Kernel 2.6.17-rc3 (currently compiling rc4+git). 32-bit ppc, ARCH=ppc with PReP target. Iptables userland binary is from the latest Debian unstable (1.3.3-2). The symptoms: iptables usually just tells Invalid Argument on any modification attempt. I'm trying to set up a simple one-rule NAT for test: iptables -t nat -A POSTROUTING -s 172.30.0.0/24 -j SNAT --to 10.0.0.1 and it usually fails but has succeeded 2 times (I now have 2 rules of this kind and they seem to just wotk once set up). Trying to delete the second rule (either by replacing -A with -D or using just -D 2) gives the same error. This should already be fixed in -rc4. Unfortunately it was still there with yesterdays rc4+git. I may have misinterpreted your report - are you running a 32bit or 64bit kernel? - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: iptables broken on ppc (ptrace too?) (2.6.17-rc3)
This should already be fixed in -rc4. Unfortunately it was still there with yesterdays rc4+git. I may have misinterpreted your report - are you running a 32bit or 64bit kernel? 32-bit kernel, this is a Motorola Powerstack II macine with 604e. PReP subarch, only buildable from the old ARCH=ppc code (not yet migrated to ARCH=powerpc). -- Meelis Roos ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: iptables broken on ppc (ptrace too?) (2.6.17-rc3)
Meelis Roos wrote: This should already be fixed in -rc4. Unfortunately it was still there with yesterdays rc4+git. I may have misinterpreted your report - are you running a 32bit or 64bit kernel? 32-bit kernel, this is a Motorola Powerstack II macine with 604e. PReP subarch, only buildable from the old ARCH=ppc code (not yet migrated to ARCH=powerpc). Ah OK, I thought it was related to the new compat code, but that isn't the case. Your trace doesn't give much clues, except that it shows that iptables dies with a SIGSEGV, which might be a bug in userspace or in the kernel. Which was the last kernel that worked for you, and can you try that version again to rule out userspace bugs? - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: iptables broken on ppc (ptrace too?) (2.6.17-rc3)
Meelis Roos wrote: Iptables seems to be broken on ppc for me. Kernel 2.6.17-rc3 (currently compiling rc4+git). 32-bit ppc, ARCH=ppc with PReP target. Iptables userland binary is from the latest Debian unstable (1.3.3-2). The symptoms: iptables usually just tells Invalid Argument on any modification attempt. I'm trying to set up a simple one-rule NAT for test: iptables -t nat -A POSTROUTING -s 172.30.0.0/24 -j SNAT --to 10.0.0.1 and it usually fails but has succeeded 2 times (I now have 2 rules of this kind and they seem to just wotk once set up). Trying to delete the second rule (either by replacing -A with -D or using just -D 2) gives the same error. This should already be fixed in -rc4. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
