All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: pud@subnet666.de
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: kernel panic with ctnetlink/nfnetlink
Date: Thu, 16 Jun 2005 03:36:33 +0200	[thread overview]
Message-ID: <42B0D7A1.70508@eurodev.net> (raw)
In-Reply-To: <20050616010225.GA18652@safetpin.homeunix.org>

pud wrote:
> On Do, 16 Jun 2005, Pablo Neira wrote:
> 
>>Please post the whole oops. Are you doing something with the conntrack
>>tool? Appreaciate a more detailled description, ruleset, etc...
> 
> sorry, i also forgot to mention that
> a) i tried recent 2.6-kernels (2.6.11, 2.6.12-rc[56])
> b) i wasn't using the conntrack tool, because it was my first try,
>     so a cronjob is still parsing /proc/net/ip_conntrack
> c) as long as the machine lives, conntrack tool is working,
>     and not causing the panic while it runs
> 
> i tried some other new modules as well (h323, ipp2p and so on),

That "so on" is rather big.

> but i'm sure it only happens if the kernel is patched with ctnetlink/nfnetlink

Why? Did you run your box *only* with ctnetlink patches applied? All 
that stuff you've mentioned is under development as well. If you patch 
your kernel with tons of experimental stuff is hard to know what's wrong.

> the whole ruleset may be too big for a list, but i can send you pm
> if you like
> 
> here the latest panic:
> 
> 
> Unable to handle kernel NULL pointer dereference

Please, decode this with ksymoops.

--
Pablo

  reply	other threads:[~2005-06-16  1:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 16:40 kernel panic with ctnetlink/nfnetlink pud
2005-06-15 23:39 ` Pablo Neira
2005-06-16  1:02   ` pud
2005-06-16  1:36     ` Pablo Neira [this message]
2005-06-16  6:43       ` Krzysztof Oledzki
2005-06-16  9:30         ` Pablo Neira
2005-06-16 10:23       ` Pablo Neira
2005-06-17  0:44       ` pud

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=42B0D7A1.70508@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pud@subnet666.de \
    /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.