From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, jolsa@redhat.com,
peterz@infradead.org, mingo@kernel.org, dsahern@gmail.com,
acme@kernel.org
Subject: Re: [PATCH v2] perf tools: fix off-by-one error in maps
Date: Tue, 14 Oct 2014 16:04:20 -0300 [thread overview]
Message-ID: <20141014190420.GB3839@redhat.com> (raw)
In-Reply-To: <8761fwh1nc.fsf@sejong.aot.lge.com>
Em Tue, Oct 07, 2014 at 02:47:19PM +0900, Namhyung Kim escreveu:
> Hi Stephane,
>
> On Mon, 6 Oct 2014 10:35:32 +0200, Stephane Eranian wrote:
> > This patch fixes off-by-one errors in the management of maps.
> > A map is defined by start address and length as implemented by map__new():
> >
> > map__init(map, type, start, start + len, pgoff, dso);
> >
> > map->start = addr;
> > map->end = end;
> >
> > Consequently, the actual address range is ]start; end[
> > map->end is the first byte outside the range. This patch
> > fixes two bugs where upper bound checking was off-by-one.
> >
> > In V2, we fix map_groups__fixup_overlappings() some more
> > where map->start was off-by-one as reported by Jiri.
>
>> It seems we also need to fix maps__find():
So I am getting this as an ack for Stephane's V2 patch and the patch
below as an extra patch, from you, acked by Stephane.
- Arnaldo
>
> diff --git a/tools/perf/util/map.c b/tools/perf/util/map.c
> index b7090596ac50..107a8c90785b 100644
> --- a/tools/perf/util/map.c
> +++ b/tools/perf/util/map.c
> @@ -752,7 +752,7 @@ struct map *maps__find(struct rb_root *maps, u64 ip)
> m = rb_entry(parent, struct map, rb_node);
> if (ip < m->start)
> p = &(*p)->rb_left;
> - else if (ip > m->end)
> + else if (ip >= m->end)
> p = &(*p)->rb_right;
> else
> return m;
>
> Thanks,
> Namhyung
>
>
> >
> > Signed-off-by: Stephane Eranian <eranian@google.com>
> > ---
> > tools/perf/util/map.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/tools/perf/util/map.c b/tools/perf/util/map.c
> > index b709059..186418b 100644
> > --- a/tools/perf/util/map.c
> > +++ b/tools/perf/util/map.c
> > @@ -556,7 +556,7 @@ struct symbol *map_groups__find_symbol_by_name(struct map_groups *mg,
> >
> > int map_groups__find_ams(struct addr_map_symbol *ams, symbol_filter_t filter)
> > {
> > - if (ams->addr < ams->map->start || ams->addr > ams->map->end) {
> > + if (ams->addr < ams->map->start || ams->addr >= ams->map->end) {
> > if (ams->map->groups == NULL)
> > return -1;
> > ams->map = map_groups__find(ams->map->groups, ams->map->type,
> > @@ -664,7 +664,7 @@ int map_groups__fixup_overlappings(struct map_groups *mg, struct map *map,
> > goto move_map;
> > }
> >
> > - before->end = map->start - 1;
> > + before->end = map->start;
> > map_groups__insert(mg, before);
> > if (verbose >= 2)
> > map__fprintf(before, fp);
> > @@ -678,7 +678,7 @@ int map_groups__fixup_overlappings(struct map_groups *mg, struct map *map,
> > goto move_map;
> > }
> >
> > - after->start = map->end + 1;
> > + after->start = map->end;
> > map_groups__insert(mg, after);
> > if (verbose >= 2)
> > map__fprintf(after, fp);
next prev parent reply other threads:[~2014-10-14 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 8:35 [PATCH v2] perf tools: fix off-by-one error in maps Stephane Eranian
2014-10-07 5:47 ` Namhyung Kim
2014-10-07 8:40 ` Stephane Eranian
2014-10-07 14:00 ` Arnaldo Carvalho de Melo
2014-10-07 14:17 ` Stephane Eranian
2014-10-07 15:10 ` Arnaldo Carvalho de Melo
2014-10-07 15:17 ` Stephane Eranian
2014-10-14 18:58 ` Arnaldo Carvalho de Melo
2014-10-14 19:03 ` Stephane Eranian
2014-10-14 19:24 ` Arnaldo Carvalho de Melo
2014-10-07 18:58 ` Chuck Ebbert
2014-10-08 15:53 ` Arnaldo Carvalho de Melo
2014-10-14 19:04 ` Arnaldo Carvalho de Melo [this message]
2014-10-15 10:05 ` [tip:perf/urgent] perf tools: Fixup off-by-one comparision in maps__find tip-bot for Namhyung Kim
2014-10-15 10:05 ` [tip:perf/urgent] perf tools: fix off-by-one error in maps tip-bot for Stephane Eranian
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=20141014190420.GB3839@redhat.com \
--to=acme@redhat.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).