All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Moises Silva <moises.silva@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Patch for H323 connection tracking for kernel 2.6.14 and Panic with SIP tracking
Date: Tue, 03 Jan 2006 12:30:38 +0100	[thread overview]
Message-ID: <43BA605E.3020801@trash.net> (raw)
In-Reply-To: <c4d05cbe0601021028x4dad0a18n2b3c1b8e10506f11@mail.gmail.com>

Moises Silva wrote:
> still getting kernel panic, copy the whole thing is a time consuming
> task, for now doing nothing, but i have downgraded the kernel to
> 2.6.13 and at least it does not kernel panics. Some one has a patch
> for sip connection tracking for kernel-2.6.14??

Most likely you need to change

         ip_ct_refresh_acct(ct, ctinfo, NULL, sip_timeout * HZ);

to

         ip_ct_refresh(ct, *pskb, sip_timeout * HZ);

in net/ipv4/netfilter/ip_conntrack_sip.c. If that doesn't help
please post the entire oops.

  reply	other threads:[~2006-01-03 11:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-31 22:47 Patch for H323 connection tracking for kernel 2.6.14 and Panic with SIP tracking Moises Silva
2006-01-02 18:28 ` Moises Silva
2006-01-03 11:30   ` Patrick McHardy [this message]
     [not found]     ` <c4d05cbe0601031235i45561171tc0ba691cf5fa417e@mail.gmail.com>
2006-01-03 20:37       ` Moises Silva
2006-01-05 20:00     ` Victor Julien
     [not found]       ` <c4d05cbe0601051220v54ab169cled8109df66cd12db@mail.gmail.com>
     [not found]         ` <43BD80C6.10603@nk.nl>
2006-01-05 21:32           ` Moises Silva
2006-01-06  9:34       ` Victor Julien
2006-01-06 11:57         ` Patrick McHardy
2006-01-06 12:18           ` Victor Julien
2006-01-07  1:50             ` Patrick McHardy
2006-01-07  9:34               ` Victor Julien
2006-01-07 16:33               ` sip connection tracking & expectations Victor Julien

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=43BA605E.3020801@trash.net \
    --to=kaber@trash.net \
    --cc=moises.silva@gmail.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.