All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Netfilter Developer Mailing List
	<netfilter-devel@lists.netfilter.org>,
	sparclinux@vger.kernel.org
Subject: Re: iptables throws unknown error - suspecting 32/64 compat issue
Date: Thu, 10 May 2007 15:20:13 +0200	[thread overview]
Message-ID: <46431C0D.5080507@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0705100832050.32349@yvahk01.tjqt.qr>

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?


WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Netfilter Developer Mailing List
	<netfilter-devel@lists.netfilter.org>,
	sparclinux@vger.kernel.org
Subject: Re: iptables throws unknown error - suspecting 32/64 compat issue
Date: Thu, 10 May 2007 13:20:13 +0000	[thread overview]
Message-ID: <46431C0D.5080507@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0705100832050.32349@yvahk01.tjqt.qr>

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?


  parent reply	other threads:[~2007-05-10 13:20 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  6:27 iptables throws unknown error - suspecting 32/64 compat issue Jan Engelhardt
2007-05-10  6:27 ` Jan Engelhardt
2007-05-10  6:34 ` Jan Engelhardt
2007-05-10  6:34   ` Jan Engelhardt
2007-05-10  7:16   ` David Miller
2007-05-10  7:16     ` David Miller
2007-05-10 13:20   ` Patrick McHardy [this message]
2007-05-10 13:20     ` Patrick McHardy
2007-05-10 13:24     ` Jan Engelhardt
2007-05-10 13:24       ` Jan Engelhardt
2007-05-10 14:02       ` Patrick McHardy
2007-05-10 14:02         ` Patrick McHardy
2007-05-10 14:05         ` Jan Engelhardt
2007-05-10 14:05           ` Jan Engelhardt
2007-05-29 21:36           ` Jan Engelhardt
2007-05-29 21:36             ` Jan Engelhardt
2007-05-29 22:29             ` Patrick McHardy
2007-05-29 22:29               ` Patrick McHardy
2007-06-02 12:54               ` Patrick McHardy
2007-06-02 12:54                 ` Patrick McHardy
2007-06-02 13:29                 ` Jan Engelhardt
2007-06-02 13:29                   ` Jan Engelhardt
2007-06-02 13:53                   ` Patrick McHardy
2007-06-02 13:53                     ` Patrick McHardy
2007-06-02 14:25                 ` Jan Engelhardt
2007-06-02 14:25                   ` Jan Engelhardt
2007-06-02 14:43                   ` Patrick McHardy
2007-06-02 14:43                     ` Patrick McHardy
2007-06-03  6:47                 ` Dmitry Mishin
2007-06-03  6:47                   ` Dmitry Mishin
2007-06-03 16:57                   ` Patrick McHardy
2007-06-03 16:57                     ` Patrick McHardy
2007-06-03 17:29                     ` Jan Engelhardt
2007-06-03 17:29                       ` Jan Engelhardt
2007-06-03 17:31                       ` Patrick McHardy
2007-06-03 17:31                         ` Patrick McHardy
2007-06-03 18:11                         ` Jan Engelhardt
2007-06-03 18:11                           ` Jan Engelhardt
2007-06-04  7:54                     ` Dmitry Mishin
2007-06-04  7:54                       ` Dmitry Mishin
2007-06-05 12:16                       ` Patrick McHardy
2007-06-05 12:16                         ` Patrick McHardy
2007-06-05 13:32                         ` Patrick McHardy
2007-06-05 13:32                           ` Patrick McHardy
2007-06-05 13:50                           ` Dmitry Mishin
2007-06-05 13:50                             ` Dmitry Mishin
2007-05-10 12:58 ` Patrick McHardy
2007-05-10 12:58   ` Patrick McHardy

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=46431C0D.5080507@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=sparclinux@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.