From: Thomas Woerner <twoerner@redhat.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Chuck Ebbert <cebbert@redhat.com>,
Netdev <netdev@vger.kernel.org>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: Still oopsing in nf_nat_move_storage()
Date: Tue, 05 Feb 2008 17:26:34 +0100 [thread overview]
Message-ID: <47A88E3A.1020407@redhat.com> (raw)
In-Reply-To: <47A44DA9.20907@trash.net>
Patrick McHardy wrote:
> Chuck Ebbert wrote:
>> On 01/31/2008 01:03 PM, Chuck Ebbert wrote:
>>> On 01/29/2008 12:18 PM, Patrick McHardy wrote:
>>>> Chuck Ebbert wrote:
>>>>> nf_nat_move_storage():
>>>>> /usr/src/debug/kernel-2.6.23/linux-2.6.23.i686/net/ipv4/netfilter/nf_nat_core.c:612
>>>>>
>>>>>
>>>>> 87: f7 47 64 80 01 00 00 testl $0x180,0x64(%edi)
>>>>> 8e: 74 39 je c9
>>>>> <nf_nat_move_storage+0x65>
>>>>>
>>>>> line 612:
>>>>> if (!(ct->status & IPS_NAT_DONE_MASK))
>>>>> return;
>>>>>
>>>>> ct is NULL
>>>> The current kernel (and 2.6.23-stable) have:
>>>>
>>>> if (!ct || !(ct->status & IPS_NAT_DONE_MASK))
>>>> return;
>>>>
>>>> so it seems you're using an old version.
>>
>> So, it is now oopsing after the test for NULL and only x86_64 is
>> catching the invalid address because it is non-canonical. Checking
>> for NULL is obviously not enough...
>
>
> Could you try whether this patch fixes it please?
>
Hallo Patrick,
I have tested the patch and the problem seems to be fixed.
Thanks,
Thomas
--
Thomas Woerner
Software Engineer Phone: +49-711-96437-0
Red Hat GmbH Fax : +49-711-96437-111
Hauptstaetterstr. 58 Email: Thomas Woerner <twoerner@redhat.com>
D-70178 Stuttgart Web : http://www.redhat.de/
prev parent reply other threads:[~2008-02-05 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 17:11 Still oopsing in nf_nat_move_storage() Chuck Ebbert
2008-01-29 17:18 ` Patrick McHardy
2008-01-31 18:03 ` Chuck Ebbert
2008-02-01 23:41 ` Chuck Ebbert
2008-02-02 10:26 ` Patrick McHardy
2008-02-02 11:02 ` Patrick McHardy
2008-02-05 16:26 ` Thomas Woerner [this message]
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=47A88E3A.1020407@redhat.com \
--to=twoerner@redhat.com \
--cc=cebbert@redhat.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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.