From: Patrick McHardy <kaber@trash.net>
To: Rainer Sabelka <sabelka@iue.tuwien.ac.at>
Cc: Krzysztof Oledzki <ole@ans.pl>, netfilter-devel@vger.kernel.org
Subject: Re: [SPAM?] Re: conntrackd causes kernel panic
Date: Wed, 11 Jun 2008 08:48:34 +0200 [thread overview]
Message-ID: <484F7542.8040906@trash.net> (raw)
In-Reply-To: <200806110841.44410.sabelka@iue.tuwien.ac.at>
Rainer Sabelka wrote:
> On Tuesday 10 June 2008 20:12:48 Krzysztof Oledzki wrote:
>> On Tue, 10 Jun 2008, Krzysztof Oledzki wrote:
>>> On Tue, 10 Jun 2008, Rainer Sabelka wrote:
>>>> On Tuesday 10 June 2008 16:29, Patrick McHardy wrote:
>>>>> Do these two patches help?
>>>> Patrick, I tried to apply those patches to the Ubuntu kernel sources
>>>> (2.6.24-18) but they failed, so I guess I should try to use a vanilla
>>>> kernel
>>>> instead.
>>>> Which version should I try?
>>> Those patches are for nf-next-2.6. I have a backport of this patches for
>>> 2.6.24.x and 2.6.25.x kernels, but I need to make sure there were no
>>> changes in the latest version.
>> OK, here it is (for 2.6.24.7):
>> ftp://ftp.ans.pl/pub/patches/patch-ole-2.6.24-o4.gz
>>
>> Not sure what changes are in ubuntu 2.6.24-18 and probably you may not
>> like to take all of my patches so:
>> ftp://ftp.ans.pl/pub/patches/broken-out/2.6.24-o4/
>>
>> You need patches 0750, 0760, 0840 and 0850.
>
> Krzysztof, I've applied these 4 patches to ubuntu's 2.6.24-18 and things look
> much better now.
> "conntrackd -c" no longer causes a kernel panic or oops.
Thanks for testing.
next prev parent reply other threads:[~2008-06-11 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 11:43 conntrackd causes kernel panic Rainer Sabelka
2008-06-10 14:29 ` Patrick McHardy
2008-06-10 15:06 ` [SPAM?] " Rainer Sabelka
2008-06-10 17:01 ` Krzysztof Oledzki
2008-06-10 18:12 ` Krzysztof Oledzki
2008-06-11 6:41 ` Rainer Sabelka
2008-06-11 6:48 ` Patrick McHardy [this message]
2008-06-11 6:17 ` 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=484F7542.8040906@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
--cc=sabelka@iue.tuwien.ac.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox