From: Jarek Poplawski <jarkao2@gmail.com>
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: Re: Inconsistend lock state in inet_frag_find
Date: Fri, 30 May 2008 10:53:34 +0000 [thread overview]
Message-ID: <20080530105334.GA7378@ff.dom.local> (raw)
In-Reply-To: <20080529120248.GA9702@alice>
On 29-05-2008 14:02, Eric Sesterhenn wrote:
> hi,
>
> the following just popped up on my test box with
> tcpsic6 -s ::1 -d ::1 -p 100000 -r 4995
>
> [ 63.616218] =================================
> [ 63.616456] [ INFO: inconsistent lock state ]
> [ 63.616456] 2.6.26-rc4 #5
> [ 63.616456] ---------------------------------
> [ 63.616456] inconsistent {softirq-on-W} -> {in-softirq-R} usage.
> [ 63.616456] tcpsic6/3869 [HC0[0]:SC1[1]:HE1:SE0] takes:
> [ 63.616456] (&f->lock){---?}, at: [<c06be62e>]
> inet_frag_find+0x1e/0x140
...
Hi,
Could you try this patch?
Regards,
Jarek P.
---
net/ipv6/netfilter/nf_conntrack_reasm.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/net/ipv6/netfilter/nf_conntrack_reasm.c b/net/ipv6/netfilter/nf_conntrack_reasm.c
index 2dccad4..f3c36d6 100644
--- a/net/ipv6/netfilter/nf_conntrack_reasm.c
+++ b/net/ipv6/netfilter/nf_conntrack_reasm.c
@@ -209,7 +209,9 @@ fq_find(__be32 id, struct in6_addr *src, struct in6_addr *dst)
arg.dst = dst;
hash = ip6qhashfn(id, src, dst);
+ local_bh_disable();
q = inet_frag_find(&nf_init_frags, &nf_frags, &arg, hash);
+ local_bh_enable();
if (q == NULL)
goto oom;
next prev parent reply other threads:[~2008-05-30 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 12:02 Inconsistend lock state in inet_frag_find Eric Sesterhenn
2008-05-30 10:53 ` Jarek Poplawski [this message]
2008-05-30 13:18 ` Eric Sesterhenn
2008-05-30 17:10 ` Jarek Poplawski
2008-05-30 21:13 ` Eric Sesterhenn
2008-05-30 21:53 ` [PATCH][NETFILTER]: fix inconsistent lock state in nf_ct_frag6_gather() Jarek Poplawski
2008-06-02 10:43 ` Patrick McHardy
2008-06-02 12:45 ` Jarek Poplawski
2008-06-02 13:24 ` 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=20080530105334.GA7378@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=snakebyte@gmx.de \
/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.