From: Christoph Lameter <cl@linux.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
kaber@trash.net, davem@davemloft.net,
Dave Jones <davej@redhat.com>,
netfilter-devel@vger.kernel.org,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: netfilter: Hung task
Date: Mon, 19 Mar 2012 11:31:47 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1203191129440.20196@router.home> (raw)
In-Reply-To: <CA+1xoqdo5zvUe+=BYr42iEEq9mU=kd1zVxrGhQc0sNYqbpBkNQ@mail.gmail.com>
On Mon, 19 Mar 2012, Sasha Levin wrote:
> On Mon, Mar 19, 2012 at 3:56 PM, Christoph Lameter <cl@linux.com> wrote:
> > This is sually something causing memory corruption. Please enable
> > debugging to get backtrace that help to debutg this. CONFIG_SLUB_DEBUG_ON
> > will do the trick or passing "slub_debug" on the kernel command line.
>
> The kernel was compiled with SLUB_DEBUG_ON, there's nothing coming out
> of the slub before that hang message, nor after it.
Ok looking at the backtrace: This is kmem_cache_destroy and not the usual
failure following a pointer in alloc / free.
netfilter calls kmem_cache_destroy which calls into sysfs functions and
there the hang occurs.
Did you try to see if lockdep can detect any serialization problems ?
Is kmem_cache_destroy called with any locks held? Interrupts off?
next prev parent reply other threads:[~2012-03-19 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 10:55 netfilter: Hung task Sasha Levin
2012-03-18 14:19 ` Pablo Neira Ayuso
2012-03-18 20:52 ` Sasha Levin
2012-03-19 0:28 ` Pablo Neira Ayuso
2012-03-19 13:56 ` Christoph Lameter
2012-03-19 16:13 ` Sasha Levin
2012-03-19 16:31 ` Christoph Lameter [this message]
2012-03-19 16:45 ` Sasha Levin
2012-03-19 20:03 ` Christoph Lameter
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=alpine.DEB.2.00.1203191129440.20196@router.home \
--to=cl@linux.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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;
as well as URLs for NNTP newsgroup(s).