From: Ingo Molnar <mingo@elte.hu>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rt21, BUG at net/ipv4/netfilter/ip_conntrack_core.c:124
Date: Sun, 26 Mar 2006 18:30:56 +0200 [thread overview]
Message-ID: <20060326163056.GC15667@elte.hu> (raw)
In-Reply-To: <1143339628.5527.3.camel@cmn2.stanford.edu>
* Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
> Hi Ingo... I'm seeing a few freezes with 2.6.15-rt21, they seem to be
> few and far between and most of the time they don't leave traces
> behind in the logs (and the reset button is the only way out). Here's
> one that apparently did leave something behind:
>
> Mar 23 15:22:48 host kernel: BUG at
> net/ipv4/netfilter/ip_conntrack_core.c:124!
does the patch below help?
Ingo
Index: linux/include/linux/netfilter_ipv4/ip_conntrack.h
===================================================================
--- linux.orig/include/linux/netfilter_ipv4/ip_conntrack.h
+++ linux/include/linux/netfilter_ipv4/ip_conntrack.h
@@ -336,7 +336,8 @@ ip_conntrack_expect_unregister_notifier(
}
extern void ip_ct_deliver_cached_events(const struct ip_conntrack *ct);
-extern void __ip_ct_event_cache_init(struct ip_conntrack *ct);
+extern void __ip_ct_event_cache_init(struct ip_conntrack_ecache *ecache,
+ struct ip_conntrack *ct);
static inline void
ip_conntrack_event_cache(enum ip_conntrack_events event,
@@ -349,7 +350,7 @@ ip_conntrack_event_cache(enum ip_conntra
local_bh_disable();
ecache = &get_cpu_var_locked(ip_conntrack_ecache, &cpu);
if (ct != ecache->ct)
- __ip_ct_event_cache_init(ct);
+ __ip_ct_event_cache_init(ecache, ct);
ecache->events |= event;
put_cpu_var_locked(ip_conntrack_ecache, cpu);
local_bh_enable();
Index: linux/net/ipv4/netfilter/ip_conntrack_core.c
===================================================================
--- linux.orig/net/ipv4/netfilter/ip_conntrack_core.c
+++ linux/net/ipv4/netfilter/ip_conntrack_core.c
@@ -114,13 +114,10 @@ void ip_ct_deliver_cached_events(const s
local_bh_enable();
}
-void __ip_ct_event_cache_init(struct ip_conntrack *ct)
+void __ip_ct_event_cache_init(struct ip_conntrack_ecache *ecache,
+ struct ip_conntrack *ct)
{
- struct ip_conntrack_ecache *ecache;
- int cpu = raw_smp_processor_id();
-
/* take care of delivering potentially old events */
- ecache = &__get_cpu_var_locked(ip_conntrack_ecache, cpu);
BUG_ON(ecache->ct == ct);
if (ecache->ct)
__ip_ct_deliver_cached_events(ecache);
next prev parent reply other threads:[~2006-03-26 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 2:20 Fernando Lopez-Lezcano
2006-03-26 16:30 ` Ingo Molnar [this message]
2006-03-26 16:34 ` Ingo Molnar
2006-03-26 20:15 ` Fernando Lopez-Lezcano
2006-03-26 23:19 ` Ingo Molnar
2006-03-27 0:33 ` Fernando Lopez-Lezcano
2006-03-29 0:11 ` Fernando Lopez-Lezcano
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=20060326163056.GC15667@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
/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
all inboxes | Powered by JetHome®