From: Rusty Russell <rusty@rustcorp.com.au>
To: glynis@butterfly.hjsoft.com
Cc: linux-kernel@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: still having smp/snat problems (Re: Linux 2.4.19-rc3)
Date: Mon, 22 Jul 2002 11:43:01 +1000 [thread overview]
Message-ID: <20020722114301.2dfcf1b8.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20020720041700.GA8172@butterfly.hjsoft.com>
On Sat, 20 Jul 2002 00:17:01 -0400
glynis@butterfly.hjsoft.com wrote:
> On Fri, Jul 19, 2002 at 09:20:49PM -0300, Marcelo Tosatti wrote:
> > <rusty@rustcorp.com.au> (02/07/17 1.630)
> > [PATCH] The real netfilter conntrack SMP overrun fix
>
> assuming this should have fixed this:
> LIST_DELETE: ip_conntrack_core.c:165
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(dd8f2e90) not in &ip_conntrack_hash
> [hash_conntrack(&ct->tuplehash[IP_CT_DIR_REPLY].tuple)].
Nope, that's the mysterious half-deleted bug.
> Gnu C gcc (GCC) 3.1.1 20020703 (Debian prerelease) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
And it's always associated with a wierd compiler version like this.
1) Does this happen reliably enough for you to decide whether something
fixes it?
2) If so, please try dropping compiler versions.
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
next prev parent reply other threads:[~2002-07-22 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 0:20 Linux 2.4.19-rc3 Marcelo Tosatti
2002-07-20 4:17 ` still having smp/snat problems (Re: Linux 2.4.19-rc3) glynis
2002-07-20 9:51 ` Martin Josefsson
2002-07-22 1:43 ` Rusty Russell [this message]
[not found] <002201c2e6e8$ee071d40$0201a8c0@intranet>
2003-03-10 15:03 ` John M Flinchbaugh
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=20020722114301.2dfcf1b8.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=glynis@butterfly.hjsoft.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox