From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Don Zickus <dzickus@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
Joe Mario <jmario@redhat.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: BUG: perf top enters loop synthesizing events for existing threads
Date: Wed, 8 Apr 2015 11:37:12 -0300 [thread overview]
Message-ID: <20150408143712.GH5403@kernel.org> (raw)
In-Reply-To: <20150408143437.GG5403@kernel.org>
Em Wed, Apr 08, 2015 at 11:34:37AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Apr 08, 2015 at 11:14:27AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Apr 08, 2015 at 07:48:23AM -0600, David Ahern escreveu:
> > > On 4/8/15 7:45 AM, Arnaldo Carvalho de Melo wrote:
> > > >>I also noticed that if I set /proc/sys/kernel/perf_event_paranoid to -1
> > > >>to run it as !root, then the problem "goes away", which I think probably
> > > >>is explained by, as !root, not being able to parse some of the /proc
> > > >>files for existing threads and thus not triggering the bug, still
> > > >>investigating...
> > >
> > > odd. because this has nothing to do with perf_events; it is just walking
> > > /proc and for the ppid adds a strstr and atoi(str). Something else is at
> > > play. I'll take a look.
> >
> > You are correcly setting the pid values, that will have effects when
> > using findnew, i.e. threads will be added to the rbtree, which causes
> > allocations, etc I.e. it is probably triggering a dormant bug
>
> Sitting there, will stop chrome to see if the problem is triggered by it...
Yeah, stopping chrome gets the system to a state that doesn't make it
trigger the bug, why it works when your patch is reverted still a
puzzle...
- Arnaldo
prev parent reply other threads:[~2015-04-08 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 13:42 BUG: perf top enters loop synthesizing events for existing threads Arnaldo Carvalho de Melo
2015-04-08 13:45 ` Arnaldo Carvalho de Melo
2015-04-08 13:48 ` David Ahern
2015-04-08 14:14 ` Arnaldo Carvalho de Melo
2015-04-08 14:34 ` Arnaldo Carvalho de Melo
2015-04-08 14:37 ` Arnaldo Carvalho de Melo [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=20150408143712.GH5403@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.com \
--cc=dzickus@redhat.com \
--cc=jmario@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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.