linux-kernel - Re: percpu: kernel BUG at mm/percpu.c:579!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <52001564.1010800@oracle.com>
Date:	Mon, 05 Aug 2013 17:13:08 -0400
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Kent Overstreet <kent.overstreet@...il.com>
CC:	Tejun Heo <tj@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
	trinity@...r.kernel.org
Subject: Re: percpu: kernel BUG at mm/percpu.c:579!

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/