linux-kernel - Re: [PATCH] Add ELF note with Linux version

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

Message-Id: <20070915013052.578554D0424@magilla.localdomain>
Date:	Fri, 14 Sep 2007 18:30:52 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Dan Aloni <da-x@...atomic.org>,
	Bernhard Walle <bwalle@...e.de>
Subject: Re: [PATCH] Add ELF note with Linux version

> Yes, binutils can be pretty fragile with notes about.  In this case it
> seems to be a specific problem with build-id; I'm not really sure what
> build-id actually does.

The thing about the build ID section that brings up issues with linking is
that it is a SHF_ALLOC, SHT_NOTE section.  As you mentioned, this is a
general, straightforward, and well-defined thing in ELF.  But in practice,
there were not previously SHF_ALLOC note sections used with custom linker
scripts like the kernel's.  (They are used every day in normal executables
and DSOs, but those don't use custom linker scripts.)

Thanks,
Roland
-
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/