mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: <acme@kernel.org>, <jolsa@kernel.org>, <namhyung@kernel.org>,
	<mingo@redhat.com>
Cc: <lizefan@huawei.com>, <pi3orama@163.com>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/2] perf: report/annotate: fix segfault problem.
Date: Tue, 7 Apr 2015 08:22:44 +0000	[thread overview]
Message-ID: <1428394966-131044-1-git-send-email-wangnan0@huawei.com> (raw)
In-Reply-To: <20150406125239.GE2500@redhat.com>

Patch v3 updates tests/kmod-path.c. It also check cpumode to filter out
strings like '[vdso]' and '[vsyscalls]' instead of directly match
against them.

'perf: kmaps: enforce usage of kmaps to protect futher bugs.' is also
posted in this series (1/2). It has a small fix: moving map__kmap() and
newly introduced map__kmaps() from map.h to map.c, because they require
pr_err and struct dso but their existance are not ensure in map.h.

Wang Nan (2):
  perf: kmaps: enforce usage of kmaps to protect futher bugs.
  perf: report/annotate: fix segfault problem.

 tools/perf/tests/kmod-path.c  | 43 +++++++++++++++++++++++++++++++++----
 tools/perf/util/dso.c         | 49 +++++++++++++++++++++++++++++++++++++------
 tools/perf/util/dso.h         | 12 ++++++-----
 tools/perf/util/header.c      |  2 +-
 tools/perf/util/machine.c     |  9 ++++++--
 tools/perf/util/map.c         | 20 ++++++++++++++++++
 tools/perf/util/map.h         |  6 ++----
 tools/perf/util/probe-event.c |  2 ++
 tools/perf/util/session.c     |  3 +++
 tools/perf/util/symbol-elf.c  | 16 +++++++++-----
 tools/perf/util/symbol.c      | 34 ++++++++++++++++++++++++------
 11 files changed, 163 insertions(+), 33 deletions(-)

-- 
1.8.3.4


  reply	other threads:[~2015-04-07  8:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03  5:56 [PATCH v2] " Wang Nan
2015-04-03  6:48 ` Ingo Molnar
2015-04-03  8:47   ` [PATCH] perf: kmaps: enforce usage of kmaps to protect futher bugs Wang Nan
2015-04-03  8:49     ` Ingo Molnar
2015-04-03 11:11     ` Jiri Olsa
2015-04-07 10:42       ` Adrian Hunter
2015-04-08 10:50         ` [PATCH v4] " Wang Nan
2015-04-03  9:07 ` [PATCH v2] perf: report/annotate: fix segfault problem Jiri Olsa
2015-04-03 10:57 ` Jiri Olsa
2015-04-06 12:52   ` Arnaldo Carvalho de Melo
2015-04-07  8:22     ` Wang Nan [this message]
2015-04-07  8:22       ` [PATCH v3 1/2] perf: kmaps: enforce usage of kmaps to protect futher bugs Wang Nan
2015-04-08 15:10         ` [tip:perf/core] perf kmaps: Check kmaps to make code more robust tip-bot for Wang Nan
2015-04-07  8:22       ` [PATCH v3 2/2] perf: report/annotate: fix segfault problem Wang Nan
2015-04-07 15:13         ` Arnaldo Carvalho de Melo
2015-04-08  3:49           ` Wang Nan
2015-04-08  3:52           ` [PATCH v4 " Wang Nan
2015-04-08 13:59             ` Jiri Olsa
2015-04-09  7:05               ` Wang Nan
2015-04-09 11:40                 ` Jiri Olsa
2015-04-09 11:52             ` Jiri Olsa
2015-04-10  1:57               ` Wang Nan
2015-04-10  2:49               ` Wang Nan
2015-04-10  3:53               ` [PATCH v5 " Wang Nan
2015-04-15  1:27                 ` Wang Nan
2015-04-20  1:18                   ` Wang Nan

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=1428394966-131044-1-git-send-email-wangnan0@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pi3orama@163.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

all inboxes | Powered by JetHome®