From: Shane Wegner <shane-keyword-kernel.a35a91@cm.nu>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 crash on Intel SDS2
Date: Mon, 17 Nov 2003 09:29:18 -0800 [thread overview]
Message-ID: <20031117172918.GA15649@cm.nu> (raw)
In-Reply-To: <Pine.LNX.4.44.0311170928330.1698-100000@logos.cnet>
On Mon, Nov 17, 2003 at 09:29:10AM -0200, Marcelo Tosatti wrote:
> > # 03/09/04 laforge@netfilter.org 1.1063.41.4
> > # [NETFILTER]: NAT range calculation fix.
> > #
> > # This patch fixes a logic bug in NAT range calculations, which also
> > # causes a large slowdown when ICMP floods go through NAT.
> > #
> > # Author: Karlis Piesenieks
> > Reversing that change has thus far fixed things over here
> > but time will tell. Is there any possible way that that
> > particular change is somehow not smp safe?
>
> That change is broken, its known to break other setups.
>
> It has been reverted in the BK tree.
I can now pretty much confirm that was the cause. I have a
19 hour uptime with pre4. Thanks for all your assistance.
Shane
next prev parent reply other threads:[~2003-11-17 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 21:05 2.4.23 crash on Intel SDS2 Shane Wegner
2003-11-10 10:46 ` Marcelo Tosatti
2003-11-12 7:07 ` Shane Wegner
2003-11-11 10:46 ` Marcelo Tosatti
2003-11-12 11:02 ` Marcelo Tosatti
2003-11-12 11:21 ` Marcelo Tosatti
2003-11-12 18:22 ` Shane Wegner
2003-11-15 12:31 ` Marcelo Tosatti
2003-11-15 20:58 ` Shane Wegner
2003-11-15 21:12 ` Willy Tarreau
2003-11-16 0:13 ` Keith Owens
2003-11-16 22:02 ` Shane Wegner
2003-11-17 11:29 ` Marcelo Tosatti
2003-11-17 17:29 ` Shane Wegner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-10 11:20 Mikael Pettersson
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=20031117172918.GA15649@cm.nu \
--to=shane-keyword-kernel.a35a91@cm.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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.