From: Gordon Messmer <yinyang@eburg.com>
Cc: Netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: kernel crash
Date: Thu, 29 May 2003 21:23:35 -0700 [thread overview]
Message-ID: <3ED6DCC7.7020302@eburg.com> (raw)
In-Reply-To: <1054247760.709.94.camel@tux.rsn.bth.se>
Martin Josefsson wrote:
>
> Beware that conntrack in kernel 2.4.20 has a serious bug caused by core
> kernel changes. Can you please try 2.4.21-rc or apply at least
> submitted/10_confirm_fix.patch from patch-o-matic and run the same thing
> again and see if it still happens?
I've suggested the patch to the person responsible for the machine (I'm
just helping him track this down).
> It appears that as if the reply-tuple is modified after the conntrack
> has been added to the hashtable (shouldn't happen). The only place this
> modification could happen is in ip_conntrack_alter_reply() which is
> called from ip_nat_setup_info() which in turn is called from various
> places to set up NAT mappings. But I can't find a place where it's
> called for a connection that's already in the hashtable...
> And the IP_NF_ASSERT() in ip_conntrack_alter_reply() would have
> triggered unless the conntrack had already been deleted from the
> lists...
Possibly memory corruption, then?
>
> Which modules are you using?
>
According to Mark:
lsmod
Module Size Used by Not tainted
ipt_MARK 856 1 (autoclean)
ipt_LOG 3320 1 (autoclean)
ipt_limit 1048 1 (autoclean)
ipt_REJECT 2840 13 (autoclean)
ipt_mark 536 1 (autoclean)
iptable_mangle 2228 1 (autoclean)
ip_nat_ftp 3696 0 (unused)
ip_conntrack_ftp 4240 1 [ip_nat_ftp]
ipt_state 632 0 (unused)
ipt_multiport 728 0 (unused)
ipt_esp 632 0 (unused)
ipt_MASQUERADE 1944 1
iptable_filter 1736 1
iptable_nat 21176 2 [ip_nat_ftp ipt_MASQUERADE]
ip_conntrack 28064 3 [ip_nat_ftp ip_conntrack_ftp ipt_state
ipt_MASQUERADE iptable_nat]
ip_tables 13400 14 [ipt_MARK ipt_LOG ipt_limit ipt_REJECT
ipt_mark iptable_mangle ipt_state
ipt_multiport ipt_esp ipt_MASQUERADE
iptable_filter iptable_nat]
ip_gre 7584 0 (unused)
sk98lin 113136 1
e1000 47980 1
next prev parent reply other threads:[~2003-05-30 4:23 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 20:41 kernel crash Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer [this message]
2003-05-30 10:53 ` Martin Josefsson
2003-05-30 10:18 ` Eicke Friedrich
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 10:24 Kernel Crash Nieścierowicz Adam
2012-05-30 17:35 Kernel crash Guido Winkelmann
2012-06-08 16:35 ` Tommi Virtanen
2011-10-06 21:59 kernel crash Pau Espin Pedrol
2011-09-22 18:45 M
2011-09-22 21:24 ` Dave Jones
2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones
2008-01-29 10:32 fenglg
2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
2008-01-29 17:59 ` Patrick McHardy
2007-12-30 18:25 Jerry Geis
2006-02-11 5:37 Kernel Crash Jayaprakash Shanmugam
2005-01-19 12:54 Kernel crash Ian Pratt
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates
2005-01-19 21:05 ` Tobias Hunger
2005-01-20 8:56 ` Keir Fraser
2005-01-20 10:00 ` Tobias Hunger
2005-01-20 11:30 ` Keir Fraser
2005-01-20 22:55 ` Tobias Hunger
2005-01-19 17:46 ` Philip R Auld
2005-01-19 1:31 Ian Pratt
2005-01-19 10:52 ` Tobias Hunger
2005-01-18 21:50 Tobias Hunger
2004-09-05 18:51 Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
2002-06-26 11:02 kernel crash Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
2001-04-02 16:40 Wayne.Brown
2001-04-01 10:15 nak
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=3ED6DCC7.7020302@eburg.com \
--to=yinyang@eburg.com \
--cc=netfilter-devel@lists.netfilter.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.