[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZGv5Fy4nmFxH5bdN@bombadil.infradead.org>
Date: Mon, 22 May 2023 16:21:59 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: Nick Alcock <nick.alcock@...cle.com>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>, masahiroy@...nel.org,
linux-modules@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-kernel@...r.kernel.org, arnd@...db.de,
akpm@...ux-foundation.org, eugene.loh@...cle.com,
kris.van.hees@...cle.com, bpf@...r.kernel.org,
Jiri Olsa <jolsa@...hat.com>
Subject: Re: [PATCH modules-next v10 00/13] kallsyms: reliable
symbol->address lookup with /proc/kallmodsyms
On Fri, May 19, 2023 at 05:50:35PM +0200, Alexander Lobakin wrote:
> FYI for devs: I posted RFC of kallsyms with file paths almost a year
> ago[0], but it went unnoticed =\
>
> `file name + function name` is not a unique pair: in one of FG-KASLR
> discussions, someone even wrote simple script, which showed around 40
> collisions in the kernel. My approach was to include file path starting
> at the kernel root folder, i.e. `net/core/dev.o:register_netdev`.
> I'm not sure why no comments happened back then tho. Maybe you could
> take a look, I'm pretty busy with other projects, but if you find
> anything useful there in the RFC, I could join to a little bit.
>
> [0]
> https://lore.kernel.org/all/20220818115306.1109642-1-alexandr.lobakin@intel.com
Petr suggested line number too, that'd fix it too.
Luis
Powered by blists - more mailing lists