All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ari Sundholm <megari@freedb.org>
To: netfilter-devel@lists.netfilter.org
Subject: Kernel panic still happens due to bug in connlimit on kernel 2.6.11
Date: Sun, 05 Jun 2005 14:54:33 +0300	[thread overview]
Message-ID: <1117972473.11871.17.camel@megaricomp> (raw)

Hello!

(Please CC me as I am not subscribed)

I recently ran into kernel panics with my shiny new 2.6.11 kernel. After
a lot of grief I found out that the connlimit module used to have a bug
which lead into an inevitable NULL pointer dereference and a panic.
After removing all iptables rules using connlimit and rebooting I got no
further panics during 48 hours - the kernel would panic in less than 10
hours when the rules were still there. This was highly suggestive that
there was still something wrong. And indeed, there was: the original
problem was never fixed!

I found out that a patch had been discussed and apparently found good
(on May 19). Someone was supposed to commit the patch. However, it seems
the patch was never committed - I took a look at the SVN trunk for
pom-ng today.

Please fix this at your earliest convenience.

Best regards,

Ari Sundholm
megari@freedb.org
Author of cddbcomp - THE Delphi component for freedb access
Moderator of freedb forums
freedb core team
Support languages: Finnish, English, German, Swedish
DISCLAIMER: Despite being part of the freedb team I only represent myself unless otherwise noted. Freedb is in no way responsible for my actions or opinions.

             reply	other threads:[~2005-06-05 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05 11:54 Ari Sundholm [this message]
2005-06-05 23:03 ` Kernel panic still happens due to bug in connlimit on kernel 2.6.11 Damon Gray
2005-06-11 15:03   ` 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=1117972473.11871.17.camel@megaricomp \
    --to=megari@freedb.org \
    --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.