From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, treeze.taeung@gmail.com,
yao.jin@linux.intel.com, kim.phillips@arm.com
Subject: Re: [RFC] perf tool: Fix memory corruption because of zero length symbols
Date: Wed, 25 Oct 2017 11:49:29 -0300 [thread overview]
Message-ID: <20171025144929.GG7045@kernel.org> (raw)
In-Reply-To: <20171025092033.qfq7ksgtfzuzu4cp@naverao1-tp.localdomain>
Em Wed, Oct 25, 2017 at 02:50:33PM +0530, Naveen N. Rao escreveu:
> On 2017/10/25 08:28AM, Jiri Olsa wrote:
> > On Tue, Oct 24, 2017 at 07:50:06PM +0530, Ravi Bangoria wrote:
> > > Perf top is often crashing at very random locations on powerpc.
> > > After investigating, I found the crash only happens when sample
> > > is of zero length symbol. Powerpc kernel has many such symbols
> > > which does not contain length details in vmlinux binary and thus
> > > start and end addresses of such symbols are same.
> > >
> > > Structure
> > >
> > > struct sym_hist {
> > > u64 nr_samples;
> > > u64 period;
> > > struct sym_hist_entry addr[0];
> > > };
> > >
> > > has last member 'addr[]' of size zero. 'addr[]' is an array of
> > > addresses that belongs to one symbol (function). If function
> > > consist of 100 instructions, 'addr' points to an array of 100
> > > 'struct sym_hist_entry' elements. For zero length symbol, it
> > > points to the *empty* array, i.e. no members in the array and
> > > thus offset 0 is also invalid for such array.
> > >
> > > static int __symbol__inc_addr_samples(...)
> > > {
> > > ...
> > > offset = addr - sym->start;
> > > h = annotation__histogram(notes, evidx);
> > > h->nr_samples++;
> > > h->addr[offset].nr_samples++;
> > > h->period += sample->period;
> > > h->addr[offset].period += sample->period;
> > > ...
> > > }
> > >
> > > Here, when 'addr' is same as 'sym->start', 'offset' becomes 0,
> > > which is valid for normal symbols but *invalid* for zero length
> > > symbols and thus updating h->addr[offset] causes memory corruption.
> >
> > I think this will work, however what's the idea behind
> > zero sized symbols? I mean when we get samples for it,
> > what are they for.. is it like alias, whats the purpose?
>
> This was discussed here:
> https://lkml.org/lkml/2016/10/10/148
>
> We aren't setting the size for our assembly routines.
Applying, after adding this as a Link: tag and Namhyung's and Jiri's
acked-by, will try to have it in perf/urgent soon, i.e. for 4.14, if
still possible.
- Arnaldo
next prev parent reply other threads:[~2017-10-25 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 14:20 [RFC] perf tool: Fix memory corruption because of zero length symbols Ravi Bangoria
2017-10-25 2:15 ` Namhyung Kim
2017-10-25 8:28 ` Jiri Olsa
2017-10-25 9:20 ` Naveen N. Rao
2017-10-25 14:49 ` Arnaldo Carvalho de Melo [this message]
2017-10-25 13:56 ` Jiri Olsa
2017-10-28 23:09 ` [tip:perf/urgent] perf symbols: " tip-bot for Ravi Bangoria
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=20171025144929.GG7045@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=treeze.taeung@gmail.com \
--cc=yao.jin@linux.intel.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