From: Kent Overstreet <kent.overstreet@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
trinity@vger.kernel.org
Subject: Re: percpu: kernel BUG at mm/percpu.c:579!
Date: Mon, 5 Aug 2013 12:15:17 -0700 [thread overview]
Message-ID: <20130805191517.GA9198@kmo-pixel> (raw)
In-Reply-To: <20130805145736.GB19631@mtj.dyndns.org>
On Mon, Aug 05, 2013 at 10:57:36AM -0400, Tejun Heo wrote:
> (cc'ing Kent, hi!)
>
> On Mon, Aug 05, 2013 at 10:49:33AM -0400, Sasha Levin wrote:
> > Hi all,
> >
> > While fuzzing with trinity inside a KVM tools guest running latest -next kernel,
> > I've stumbled on the following spew:
> >
> > [ 274.820724] ------------[ cut here ]------------
> > [ 274.821320] kernel BUG at mm/percpu.c:579!
>
> Looks like double free.
>
> > [ 274.821848] invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
> > [ 274.822467] Modules linked in:
> > [ 274.823240] CPU: 13 PID: 58 Comm: rcuos/13 Tainted: G W
> > 3.11.0-rc4-next-20130805-sasha-00002-gf6cc217 #3975
> > [ 274.824464] task: ffff880220cb3000 ti: ffff880220cba000 task.ti: ffff880220cba000
> > [ 274.825442] RIP: 0010:[<ffffffff812417b8>] [<ffffffff812417b8>] pcpu_free_area+0xd8/0x1e0
> > [ 274.826470] RSP: 0018:ffff880220cbbc58 EFLAGS: 00010002
> > [ 274.827316] RAX: ffff8800c9e3abd4 RBX: 00000000000002f5 RCX: 00000000000002f5
> > [ 274.828162] RDX: 0000000000000004 RSI: 000000000000ede0 RDI: 000000000000ede0
> > [ 274.829270] RBP: ffff880220cbbc78 R08: 0000000000000324 R09: ffff8800c9e3a000
> > [ 274.830102] R10: ffff8800c9e3a000 R11: 0000000000000000 R12: ffff88022049ff80
> > [ 274.830102] R13: 0000000000000bd4 R14: 0000000000000012 R15: ffffffff86612060
> > [ 274.831367] FS: 0000000000000000(0000) GS:ffff880226000000(0000) knlGS:0000000000000000
> > [ 274.831367] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> > [ 274.831367] CR2: 0000000001253028 CR3: 0000000214aff000 CR4: 00000000000006e0
> > [ 274.831367] Stack:
> > [ 274.831367] 0000000000000282 000000000000ede0 ffff88022049ff80 000060fdd980ede0
> > [ 274.831367] ffff880220cbbca8 ffffffff81241c7e ffff880220cbbca8 ffff8800b80f83e0
> > [ 274.831367] 0000000000000000 ffff8800b80f83c0 ffff880220cbbd18 ffffffff81a14ea6
> > [ 274.831367] Call Trace:
> > [ 274.831367] [<ffffffff81241c7e>] free_percpu+0x9e/0x160
> > [ 274.831367] [<ffffffff81a14ea6>] percpu_ref_kill_rcu+0xb6/0x1b0
>
> 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...
WARNING: multiple messages have this Message-ID (diff)
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
trinity@vger.kernel.org
Subject: Re: percpu: kernel BUG at mm/percpu.c:579!
Date: Mon, 5 Aug 2013 12:15:17 -0700 [thread overview]
Message-ID: <20130805191517.GA9198@kmo-pixel> (raw)
In-Reply-To: <20130805145736.GB19631@mtj.dyndns.org>
On Mon, Aug 05, 2013 at 10:57:36AM -0400, Tejun Heo wrote:
> (cc'ing Kent, hi!)
>
> On Mon, Aug 05, 2013 at 10:49:33AM -0400, Sasha Levin wrote:
> > Hi all,
> >
> > While fuzzing with trinity inside a KVM tools guest running latest -next kernel,
> > I've stumbled on the following spew:
> >
> > [ 274.820724] ------------[ cut here ]------------
> > [ 274.821320] kernel BUG at mm/percpu.c:579!
>
> Looks like double free.
>
> > [ 274.821848] invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
> > [ 274.822467] Modules linked in:
> > [ 274.823240] CPU: 13 PID: 58 Comm: rcuos/13 Tainted: G W
> > 3.11.0-rc4-next-20130805-sasha-00002-gf6cc217 #3975
> > [ 274.824464] task: ffff880220cb3000 ti: ffff880220cba000 task.ti: ffff880220cba000
> > [ 274.825442] RIP: 0010:[<ffffffff812417b8>] [<ffffffff812417b8>] pcpu_free_area+0xd8/0x1e0
> > [ 274.826470] RSP: 0018:ffff880220cbbc58 EFLAGS: 00010002
> > [ 274.827316] RAX: ffff8800c9e3abd4 RBX: 00000000000002f5 RCX: 00000000000002f5
> > [ 274.828162] RDX: 0000000000000004 RSI: 000000000000ede0 RDI: 000000000000ede0
> > [ 274.829270] RBP: ffff880220cbbc78 R08: 0000000000000324 R09: ffff8800c9e3a000
> > [ 274.830102] R10: ffff8800c9e3a000 R11: 0000000000000000 R12: ffff88022049ff80
> > [ 274.830102] R13: 0000000000000bd4 R14: 0000000000000012 R15: ffffffff86612060
> > [ 274.831367] FS: 0000000000000000(0000) GS:ffff880226000000(0000) knlGS:0000000000000000
> > [ 274.831367] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> > [ 274.831367] CR2: 0000000001253028 CR3: 0000000214aff000 CR4: 00000000000006e0
> > [ 274.831367] Stack:
> > [ 274.831367] 0000000000000282 000000000000ede0 ffff88022049ff80 000060fdd980ede0
> > [ 274.831367] ffff880220cbbca8 ffffffff81241c7e ffff880220cbbca8 ffff8800b80f83e0
> > [ 274.831367] 0000000000000000 ffff8800b80f83c0 ffff880220cbbd18 ffffffff81a14ea6
> > [ 274.831367] Call Trace:
> > [ 274.831367] [<ffffffff81241c7e>] free_percpu+0x9e/0x160
> > [ 274.831367] [<ffffffff81a14ea6>] percpu_ref_kill_rcu+0xb6/0x1b0
>
> 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...
next prev parent reply other threads:[~2013-08-05 19:15 UTC|newest]
Thread overview: 6+ 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 14:57 ` Tejun Heo
2013-08-05 19:15 ` Kent Overstreet [this message]
2013-08-05 19:15 ` Kent Overstreet
2013-08-05 21:13 ` Sasha Levin
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=20130805191517.GA9198@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--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 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.