linux-kernel - Re: [GIT PULL] x86 setup: correct booting on 486 (revised)

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: <47309608.9030200@zytor.com>
Date:	Tue, 06 Nov 2007 08:27:52 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Mikael Petterson <mikpe@...uu.se>
Subject: Re: [GIT PULL] x86 setup: correct booting on 486 (revised)

Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> The ELF note format is sane enough, although it looks like it's not
>> self-terminating, so we'd either need an offset and a length field, or
>> adopt the convention that namesz = descsz = type = 0 terminates the
>> block (I prefer the latter, myself.)
> 
> Hm, I think offset+length would be better: it's how they're represented
> in a normal ELF file, so you can just extract the length if you're
> extracting the notes.  Also, generating a terminating note with the
> current linker-based notes machinery would be a bit of a pain.

.notes : {
	*(.note.*)
	. = ALIGN(4);
	LONG(0);
	LONG(0);
	LONG(0);
}

Am I missing something?

-
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/