From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: 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, Christoph Lameter <cl@linux.com>
Subject: Re: netfilter: Hung task
Date: Mon, 19 Mar 2012 01:28:11 +0100 [thread overview]
Message-ID: <20120319002811.GA30408@1984> (raw)
In-Reply-To: <CA+1xoqcQYqCgQb=1M5PVkm=6SBhV2oJxJ2CtBp=gAvZM36Kc2Q@mail.gmail.com>
On Sun, Mar 18, 2012 at 10:52:55PM +0200, Sasha Levin wrote:
> On Sun, Mar 18, 2012 at 4:19 PM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > On Sun, Mar 18, 2012 at 12:55:13PM +0200, Sasha Levin wrote:
> >> Hi all,
> >>
> >> I got the following spew after fuzzing using trinity on a KVM tools
> >> guest, using the latest linux-next.
> >>
> >> It reminds me a lot of https://lkml.org/lkml/2012/3/14/375 and
> >> https://lkml.org/lkml/2012/1/14/45
> >
> > You mention neither Linux kernel version nor the way you trigger this.
> >
> > With that little information it's really hard to really know.
>
> Hum? I've mentioned it happened with "the latest linux-next" (which is
> currently two days old), and using the trinity fuzzer - which means
> that I don't have a specific method to reproduce the problem.
Sorry, I should not read my email diagonally, really.
Looking at the trace, I'd point to some problem in the slub memory
allocator. Please, correct me if I'm wrong.
Christoph?
next prev parent reply other threads:[~2012-03-19 0:28 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 [this message]
2012-03-19 13:56 ` Christoph Lameter
2012-03-19 16:13 ` Sasha Levin
2012-03-19 16:31 ` Christoph Lameter
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=20120319002811.GA30408@1984 \
--to=pablo@netfilter.org \
--cc=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 \
/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).