From: Patrick McHardy <kaber@trash.net>
To: Thomas Woerner <twoerner@redhat.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: kernel crash in nf_nat_move_storage
Date: Wed, 30 Jan 2008 17:33:32 +0100 [thread overview]
Message-ID: <47A0A6DC.8030404@trash.net> (raw)
In-Reply-To: <47A0A4C6.4040705@redhat.com>
Thomas Woerner wrote:
> 2.6.24 seems to be ok on i386 also, but on x86_64 it is crashing.
>
> Thomas Woerner wrote:
>> Hello Patrick,
>>
>> after sucessfully testing 2.6.23.14-107.fc8 on my i386 test system, I
>> installed 2.6.23.14-107.fc8 on the x86_64 system. At first I was not
>> able to reproduce the problem, but after starting the ftp server
>> (vsftpd) and using 'echo "quit" | telnet test-x86_64 80' several
>> times, I got a backtrace again. Please have a look at the attachment.
Thats odd, I can't see a reason why it would crash on x86_64.
Could you add a few printks to nf_nat_move_storage to print
out the pointers?
prev parent reply other threads:[~2008-01-30 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 11:42 kernel crash in nf_nat_move_storage Thomas Woerner
2008-01-30 13:30 ` Patrick McHardy
2008-01-30 15:50 ` Thomas Woerner
2008-01-30 16:24 ` Thomas Woerner
2008-01-30 16:33 ` Patrick McHardy [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=47A0A6DC.8030404@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=twoerner@redhat.com \
/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.