From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Thomas Jarosch <thomas.jarosch@intra2net.com>
Subject: Re: [GIT PULL 0/5] perf/core improvements and fixes
Date: Sat, 15 Oct 2011 13:09:32 -0600 [thread overview]
Message-ID: <4E99DA6C.3030906@gmail.com> (raw)
In-Reply-To: <20111015190620.GA21352@ghostprotocols.net>
On 10/15/2011 01:06 PM, Arnaldo Carvalho de Melo wrote:
>>
>> It should. The message comes from map__load() when it detects a deleted
>> mapping such as:
>>
>> 7f9e8d5c7000-7f9e8d5c8000 rw-p 0000c000 fd:02 1046947
>> /lib64/libpam.so.0.82.2.#prelink#.cM3f72 (deleted)
>>
>> I have removed prelink from most of my systems (managed to find one lone
>> server with the above).
>
> David,
>
> Can you send me a patch that clarifies this situation?
>
> - Arnaldo
Clarifies in what way? The code checks for "(deleted)" on the dso and
suggests a restart of the process.
David
next prev parent reply other threads:[~2011-10-15 19:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 18:27 [GIT PULL 0/5] perf/core improvements and fixes Arnaldo Carvalho de Melo
2011-10-14 18:27 ` [PATCH 1/5] perf hists browser: Invalidate ui_browser->top after timer calls Arnaldo Carvalho de Melo
2011-10-14 18:27 ` [PATCH 2/5] perf annotate browser: Exit when pressing ESC or the left arrow Arnaldo Carvalho de Melo
2011-10-14 18:27 ` [PATCH 3/5] perf ui browser: Add filter method Arnaldo Carvalho de Melo
2011-10-14 18:27 ` [PATCH 4/5] perf annotate browser: Allow toggling the visualization of source code lines Arnaldo Carvalho de Melo
2011-10-14 18:27 ` [PATCH 5/5] perf buildid: Fix possible unterminated readlink() result buffer Arnaldo Carvalho de Melo
2011-10-15 14:59 ` [GIT PULL 0/5] perf/core improvements and fixes Ingo Molnar
2011-10-15 17:00 ` David Ahern
2011-10-15 17:04 ` Ingo Molnar
2011-10-15 17:46 ` David Ahern
2011-10-15 19:06 ` Arnaldo Carvalho de Melo
2011-10-15 19:09 ` David Ahern [this message]
2011-10-17 1:15 ` Arnaldo Carvalho de Melo
2011-10-17 6:48 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2018-02-21 1:34 Arnaldo Carvalho de Melo
2018-02-21 7:52 ` Ingo Molnar
2015-10-21 21:31 Arnaldo Carvalho de Melo
2015-10-22 7:34 ` Ingo Molnar
2015-10-07 22:45 Arnaldo Carvalho de Melo
2015-04-13 22:14 Arnaldo Carvalho de Melo
2015-04-13 22:33 ` Masami Hiramatsu
2015-04-13 23:09 ` Arnaldo Carvalho de Melo
2015-04-13 23:19 ` Arnaldo Carvalho de Melo
2015-04-14 12:12 ` Ingo Molnar
2014-10-17 19:49 Arnaldo Carvalho de Melo
2014-10-18 7:04 ` Ingo Molnar
2014-06-27 12:20 Jiri Olsa
2014-07-05 9:30 ` Ingo Molnar
2014-04-18 10:31 Jiri Olsa
2011-02-17 20:41 Arnaldo Carvalho de Melo
2011-02-18 7:26 ` Ingo Molnar
2010-12-06 20:28 Arnaldo Carvalho de Melo
2010-11-26 21:47 Arnaldo Carvalho de Melo
2010-10-23 20:28 Arnaldo Carvalho de Melo
2010-10-24 9:39 ` Ingo Molnar
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=4E99DA6C.3030906@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=thomas.jarosch@intra2net.com \
/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;
as well as URLs for NNTP newsgroup(s).