linux-kernel - Re: [RFC PATCH 3/3] kallsyms: add option to include relative filepaths into kallsyms

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-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 18 Aug 2022 14:23:43 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Alexander Lobakin <alexandr.lobakin@...el.com>
Cc:     linux-kernel@...r.kernel.org,
        Masahiro Yamada <masahiroy@...nel.org>,
        Michal Marek <michal.lkml@...kovi.net>,
        "Naveen N. Rao" <naveen.n.rao@...ux.ibm.com>,
        Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
        "David S. Miller" <davem@...emloft.net>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Josh Poimboeuf <jpoimboe@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Jiri Kosina <jikos@...nel.org>,
        Miroslav Benes <mbenes@...e.cz>,
        Petr Mladek <pmladek@...e.com>,
        Joe Lawrence <joe.lawrence@...hat.com>,
        linux-kbuild@...r.kernel.org, live-patching@...r.kernel.org,
        lkp@...el.com, stable@...r.kernel.org
Subject: Re: [RFC PATCH 3/3] kallsyms: add option to include relative
 filepaths into kallsyms

On Thu, Aug 18, 2022 at 01:53:06PM +0200, Alexander Lobakin wrote:
> Currently, kallsyms kernel code copes with symbols with the same
> name by indexing them according to their position in vmlinux and
> requiring to provide an index of the desired symbol. This is not
> really quite reliable and is fragile to any features performing
> symbol or section manipulations such as FG-KASLR.

Ah, here's the reasoning, stuff like this should go into the 0/X message
too, right?

Anyway, what is currently broken that requires this?  What will this
make easier in the future?  What in the future will depend on this?

> So, in order to make kallsyms immune to object code modification

What do you mean by "object code modification"?

Can that happen now?  What causes it?  What happens if it does happen?

And why are any of these being cc:ed to the stable mailing list?

confused,

greg k-h