From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf symbols: Fix reading build id
Date: Fri, 22 Jul 2016 09:34:35 +0200 [thread overview]
Message-ID: <20160722073435.GP5368@pengutronix.de> (raw)
In-Reply-To: <20160721075302.GA7651@krava>
On Thu, Jul 21, 2016 at 09:53:02AM +0200, Jiri Olsa wrote:
> On Thu, Jul 21, 2016 at 09:21:55AM +0200, Marc Kleine-Budde wrote:
> > On 07/21/2016 09:09 AM, Uwe Kleine-König wrote:
> > > From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > >
> > > When is_regular_file(name) is called name points to a freshly allocated
> > > and uninitialized chunk of memory, so is_regular_file(name) is usually
> > > false and reading build id is skipped which makes it impossible to
> > > find debug infos when a build id based system is in use.
> > >
> > > Fixes: 403567217d3f ("perf symbols: Do not read symbols/data from device files")
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> >
> > See https://patchwork.kernel.org/patch/9196777/
>
> Arnaldo, could you please pull this one in?
It is in next as ed7b630b310775f3b6c0b360ede7a12cd8dff6fe. Does "pull
in" mean "send it to Linus for 4.7"? (That's what I'd consider
approriate.)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2016-07-22 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 7:09 [PATCH] perf symbols: Fix reading build id Uwe Kleine-König
2016-07-21 7:21 ` Marc Kleine-Budde
2016-07-21 7:53 ` Jiri Olsa
2016-07-22 7:34 ` Uwe Kleine-König [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=20160722073435.GP5368@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mkl@pengutronix.de \
--cc=peterz@infradead.org \
--cc=uwe@kleine-koenig.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 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).