From: Andi Kleen <[email protected]>

Currently perf record always errors out when you run it as non-root
with kptr_restrict == 1, which is often the default.

Make it only warn instead and fix the kernel resolve code
to not segfault later. Profiling works still fine, except
kernel symbols are not resolved.

Signed-off-by: Andi Kleen <[email protected]>
---
 tools/perf/util/event.c   | 8 ++++++--
 tools/perf/util/session.c | 2 +-
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
index ed55819..4af6b27 100644
--- a/tools/perf/util/event.c
+++ b/tools/perf/util/event.c
@@ -558,13 +558,17 @@ int perf_event__synthesize_kernel_mmap(struct perf_tool 
*tool,
        struct map *map;
        struct kmap *kmap;
        int err;
+       union perf_event *event;
+
+       if (machine->vmlinux_maps[0] == NULL)
+               return -1;
+
        /*
         * We should get this from /sys/kernel/sections/.text, but till that is
         * available use this, and after it is use this as a fallback for older
         * kernels.
         */
-       union perf_event *event = zalloc((sizeof(event->mmap) +
-                                         machine->id_hdr_size));
+       event = zalloc((sizeof(event->mmap) + machine->id_hdr_size));
        if (event == NULL) {
                pr_debug("Not enough memory synthesizing mmap event "
                         "for kernel modules\n");
diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
index 6d2d50d..883406f 100644
--- a/tools/perf/util/session.c
+++ b/tools/perf/util/session.c
@@ -119,7 +119,7 @@ struct perf_session *perf_session__new(struct 
perf_data_file *file,
                 * kernel MMAP event, in perf_event__process_mmap().
                 */
                if (perf_session__create_kernel_maps(session) < 0)
-                       goto out_delete;
+                       pr_warning("Cannot read kernel map\n");
        }
 
        if (tool && tool->ordering_requires_timestamps &&
-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to