From: Eric Dumazet <eric.dumazet@gmail.com>
To: "\"Oleg A. Arkhangelsky\"" <sysoleg@yandex.ru>
Cc: Changli Gao <xiaosuo@gmail.com>,
Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
Paul E McKenney <paulmck@linux.vnet.ibm.com>
Subject: Re: Kernel panic nf_nat_setup_info+0x5b3/0x6e0
Date: Thu, 31 Mar 2011 16:47:52 +0200 [thread overview]
Message-ID: <1301582872.3169.44.camel@edumazet-laptop> (raw)
In-Reply-To: <586191301580222@web107.yandex.ru>
Le jeudi 31 mars 2011 à 18:03 +0400, "Oleg A. Arkhangelsky" a écrit :
>
> 26.03.2011, 16:44, "Changli Gao" <xiaosuo@gmail.com>:
> > On Thu, Mar 3, 2011 at 3:33 PM, Changli Gao <xiaosuo@gmail.com>; wrote:
> >
> >> Please try the patch attached and test if the problem is solved or not. Thanks.
> >
> > Any feedback? Thanks.
> >
>
> Seems that patch is fine.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=21512
>
I wonder if this is not hiding another bug.
Adding an RCU grace period might reduce the probability window.
By the time nf_conntrack_free(ct) is called, no other cpu/thread
could/should use ct, or ct->ext ?
Sure, another thread can find/pass_on ct in a lookup but should not use
it, since its refcount (ct_general.use) should be 0.
Patrick ?
next prev parent reply other threads:[~2011-03-31 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:07 Kernel panic nf_nat_setup_info+0x5b3/0x6e0 "Oleg A. Arkhangelsky"
2011-03-02 11:37 ` Patrick McHardy
2011-03-02 14:37 ` Changli Gao
2011-03-02 19:50 ` "Oleg A. Arkhangelsky"
2011-03-03 7:33 ` Changli Gao
2011-03-26 15:44 ` Changli Gao
2011-03-31 14:03 ` "Oleg A. Arkhangelsky"
2011-03-31 14:47 ` Eric Dumazet [this message]
2011-04-01 2:02 ` Changli Gao
2011-04-01 5:30 ` Eric Dumazet
2011-04-05 11:49 ` Patrick McHardy
2011-05-21 15:42 ` Changli Gao
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=1301582872.3169.44.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sysoleg@yandex.ru \
--cc=xiaosuo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox