Jan Engelhardt wrote: > On May 10 2007 08:27, Jan Engelhardt wrote: > >>As mentioned in the topic, I suspect it is due to 32-bit iptables not >>coping correctly with the 64-bit kernel (sometimes, patches to fix these >>are posted, so I thought it could be related). OS is Aurora Linux 2.98, >>with their latest(?) kernel 2.6.20-1.2986.al3.3smp. > > > And the following cmd oopsed it: > > # iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW > -j sshcheck; I believe this is a bug in the compat code, which *seems* to call (its a bit messy, I just had a quick look) the destroy function without having called checkentry previously when something goes wrong. Which commands did you run before this? - To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
