All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raivis Bucis <raivis@mt.lv>
To: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: kernel crash [problem with helpers]
Date: Wed, 26 May 2004 14:12:32 +0300	[thread overview]
Message-ID: <200405261412.32587.raivis@mt.lv> (raw)

ip_conntrack assumes that expect->expectant->helper allways will be non null, 
but that is not allways the case.

When tftp conntrack is used, on first received UDP packet, tfp helper adds 
expectation. If it gets NATed later to some other port, 
ip_conntrack_alter_reply will set its helper to NULL, but expectation is 
still kept, and when expected conntrack is created, its master conntrack 
doesn't have helper anymore. This leads to kernel oops in list_conntracks 
when reading "/proc/net/ip_conntrack", etc.

Therefore I propose following fix:

diff -u -r1.13 ip_conntrack_core.c
--- ip_conntrack_core.c 9 Jan 2004 07:52:10 -0000       1.13
+++ ip_conntrack_core.c 26 May 2004 11:05:23 -0000
@@ -1139,10 +1139,13 @@
        DUMP_TUPLE(newreply);

        conntrack->tuplehash[IP_CT_DIR_REPLY].tuple = *newreply;
-       if (!conntrack->master)
-               conntrack->helper = LIST_FIND(&helpers, helper_cmp,
-                                             struct ip_conntrack_helper *,
-                                             newreply);
+       if (!conntrack->master) {
+               struct ip_conntrack_helper *newhelper;
+               newhelper = LIST_FIND(&helpers, helper_cmp,
+                                     struct ip_conntrack_helper *,
+                                     newreply);
+               if (newhelper) conntrack->helper = newhelper;
+       }
        WRITE_UNLOCK(&ip_conntrack_lock);

        return 1;


Or maybe, we should check whether it has expectations before looking for new 
helper.

Raivis Bucis

             reply	other threads:[~2004-05-26 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 11:12 Raivis Bucis [this message]
2004-05-27  0:34 ` kernel crash [problem with helpers] 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=200405261412.32587.raivis@mt.lv \
    --to=raivis@mt.lv \
    --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.