From: Sasha Levin <sasha.levin@oracle.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
trinity@vger.kernel.org
Subject: Re: percpu: kernel BUG at mm/percpu.c:579!
Date: Mon, 05 Aug 2013 17:13:08 -0400 [thread overview]
Message-ID: <52001564.1010800@oracle.com> (raw)
In-Reply-To: <20130805191517.GA9198@kmo-pixel>
On 08/05/2013 03:15 PM, Kent Overstreet wrote:
>> From percpu_ref release path. Kent?
> From the backtrace I have no idea if this was from the aio code using it
> or the cgroup code - Sasha, any idea?
>
> AIO is probably more likely, I'm going to look to see if I can find
> anything...
I honestly don't know. It ran under trinity so I'm not sure what the exact
scenario is.
I can't seem to hit it again easily so far, it seems that many people merged their
work in the -next tree recently so I'm seeing multiple unrelated failures all over
the place, which makes reproducing this one harder.
Thanks,
Sasha
prev parent reply other threads:[~2013-08-05 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 14:49 percpu: kernel BUG at mm/percpu.c:579! Sasha Levin
2013-08-05 14:57 ` Tejun Heo
2013-08-05 19:15 ` Kent Overstreet
2013-08-05 21:13 ` Sasha Levin [this message]
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=52001564.1010800@oracle.com \
--to=sasha.levin@oracle.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=trinity@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