All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Peter Olsson <aa@tbh.se>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Kernel Oops with kernel 2.4.25 and iptables 1.2.9 in __unexpect_related
Date: Tue, 15 Jun 2004 10:31:22 +0200	[thread overview]
Message-ID: <40CEB3DA.5070401@trash.net> (raw)
In-Reply-To: <002401c452ac$06523580$7c01a8c0@std.visionutv.se>

Peter Olsson wrote:
> After running my firewall without any problems for about 90 days, I 
> suddenly got a Kernel Oops.
> When running it through ksymoops I received the result below.
>  
> I've read a few comments about a bug in the newnat code in 
> unexpect_related, but what I can see
> this should be fixed a long time ago, and if I compare the 
> unexpect_related calls in the ip_conntrack_core.c
> from version 2.4.25 til 2.4.26 they work in exactly the same way. Could 
> there be something else causing
> this problem? I don't think it's hardware related, I've been using the 
> same hardware, but with kernel 2.4.27
> for about a year before this happened, and it's been working really good.

We are at 2.4.27-pre5 now ..

It looks like the list is uninitialized in list_del. Have you applied
any other patches besides pptp_conntrack_nat ?

Regards
Patrick

  reply	other threads:[~2004-06-15  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15  7:40 Kernel Oops with kernel 2.4.25 and iptables 1.2.9 in __unexpect_related Peter Olsson
2004-06-15  8:31 ` Patrick McHardy [this message]
2004-06-15 17:44   ` Peter Olsson
2004-06-15 18:06     ` Patrick McHardy
2004-06-15 20:11       ` Peter Olsson
2004-06-15 22:07         ` Henrik Nordstrom
2004-06-16 15:57           ` Peter Olsson

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=40CEB3DA.5070401@trash.net \
    --to=kaber@trash.net \
    --cc=aa@tbh.se \
    --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.