linux-kernel - Re: [RFC 28/31] x86/alternative: Create symbols for special section entries

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]

Message-ID: <20240904161313.p537aq2vbmuli6bj@treble>
Date: Wed, 4 Sep 2024 09:13:13 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: live-patching@...r.kernel.org, linux-kernel@...r.kernel.org,
	x86@...nel.org, Miroslav Benes <mbenes@...e.cz>,
	Petr Mladek <pmladek@...e.com>,
	Joe Lawrence <joe.lawrence@...hat.com>,
	Jiri Kosina <jikos@...nel.org>,
	Marcos Paulo de Souza <mpdesouza@...e.com>,
	Song Liu <song@...nel.org>
Subject: Re: [RFC 28/31] x86/alternative: Create symbols for special section
 entries

On Wed, Sep 04, 2024 at 10:08:42AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 03, 2024 at 09:28:29PM -0700, Josh Poimboeuf wrote:
> > Take a more generic approach: for the "array of structs" style sections,
> > annotate each struct entry with a symbol containing the entry.  This
> > makes it easy for tooling to parse the data and avoids the fragility of
> > hardcoding section details.
> > 
> > (For the "array of pointers" style sections, no symbol is needed, as the
> > format is already self-evident.)
> 
> (so someone went and touched a ton of the alternative code recently,
> this is going to need a rebase)
> 
> This generates a metric ton of symbols and I'm not seeing you touch
> kallsyms.c, do we want to explicitly drop these from a --all-symbols
> build? I don't think it makes sense to have them in the final image,
> right?

Yes, good point.

-- 
Josh