linux-kernel - perf tools: Question about kmem and kernel symbol resolution

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAM9d7ci1grg4NSMJahr-zjo+v8CkumbnwREhjkc+o6y9kYuaGw@mail.gmail.com>
Date:	Thu, 31 Jul 2014 17:35:32 +0900
From:	Namhyung Kim <namhyung@...il.com>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jiri Olsa <jolsa@...hat.com>
Subject: perf tools: Question about kmem and kernel symbol resolution

Hi,

I'm looking kernel symbol mismatch issue, and found something in perf
kmem code.  The commit e727ca73f85d ("perf kmem: Resolve kernel
symbols again") added perf_session__create_kernel_maps() but I don't
know why.  Why did it miss the MMAP event?

I think if we create a kernel maps at report time, it might not match
to samples in a perf.data if it's recorded on a different kernel.
This is the main reason of the mismatch problem I'm currently chasing
IMHO.  What am I missing?

Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/