linux-kernel - Re: perf counter issue - WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 May 2009 19:37:53 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	vatsa@...ibm.com
Cc:	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Mike Galbraith <efault@....de>,
	Thomas Gleixner <tglx@...utronix.de>,
	Paul Mackerras <paulus@...ba.org>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: perf counter issue -
 WARN_ON_ONCE(!list_empty(&tsk->perf_counter_ctx.counter_list));

On Fri, 2009-05-15 at 18:13 +0200, Peter Zijlstra wrote:
> On Fri, 2009-05-15 at 21:28 +0530, Srivatsa Vaddagiri wrote:
> > On Fri, May 15, 2009 at 11:51:44AM -0300, Arnaldo Carvalho de Melo wrote:
> > > > hm, is there a reproducer perhaps? Is there some class file i could 
> > > > run with specific parameters to reproduce it?
> > > 
> > > I'll try this with some java benchmarks we have, AMQP related, lets see
> > > if I can reproduce it.
> > 
> > I tried this with SPECJbb - which I am not at liberty to distribute
> > unfortunately. I will try and recreate it with volanomark or other open
> > source benchmarks.
> 
> I could indeed reproduce with vmark. Am poking at it.. still clueless
> though ;-)

[root@...eron tmp]# cat foo.c
#include <pthread.h>
#include <unistd.h>

void *thread(void *arg)
{
        sleep(5);
        return NULL;
}

void main(void)
{
        pthread_t thr;
        pthread_create(&thr, NULL, thread, NULL);
}

The above instantly triggers it. It appears we fail to cleanup on the
reparent path. I'll go root around in exit.c.

--
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/