All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: netfilter-devel@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bug 10875] Oops in nf_nat_setup_info
Date: Sat, 07 Jun 2008 17:27:33 +0200	[thread overview]
Message-ID: <484AA8E5.2040704@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0806071656190.10202@bizon.gios.gov.pl>

Krzysztof Oledzki wrote:
> 
> 
> On Sat, 7 Jun 2008, Patrick McHardy wrote:
> 
>> Krzysztof Oledzki wrote:
>>> On Sat, 7 Jun 2008, Patrick McHardy wrote:
>>>> In case its not, does that kernel include commit 86577c661?
>>>
>>> No, it does not but unfortunately this fix does not solve the crash. 
>>> However, before you spend too much time on this I'll check 2.6.25.6 
>>> and 2.6.26-rc to make sure this problem has not been solved already.
>>
>> Thanks, please let me know how it turns out.
> 
> Clean 2.6.26-rc5 kernel, no additional patches at all.
> 
> BUG: unable to handle kernel NULL pointer dereference at 00000032
> IP: [<c03d930e>] nf_nat_setup_info+0x219/0x57f
> *pde = 00000000 Oops: 0000 [#1] PREEMPT SMP


How heavily is that system loaded (conntrack-wise)?

  reply	other threads:[~2008-06-07 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 18:05 [Bug 10875] Oops in nf_nat_setup_info Krzysztof Oledzki
2008-06-06 22:47 ` Krzysztof Oledzki
2008-06-07 12:01   ` Patrick McHardy
2008-06-07 12:05     ` Patrick McHardy
2008-06-07 13:51       ` Krzysztof Oledzki
2008-06-07 13:54         ` Patrick McHardy
2008-06-07 14:58           ` Krzysztof Oledzki
2008-06-07 15:27             ` Patrick McHardy [this message]
2008-06-07 15:34               ` Krzysztof Oledzki
2008-06-07 13:27     ` Krzysztof Oledzki

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=484AA8E5.2040704@trash.net \
    --to=kaber@trash.net \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=ole@ans.pl \
    /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.