linux-kernel - Re: [PATCH 02/02] Elf: Align elf notes properly

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 10 Nov 2006 15:39:30 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jeremy@...p.org
Cc:	magnus.damm@...il.com, horms@...ge.net.au, ebiederm@...ssion.com,
	magnus@...inux.co.jp, linux-kernel@...r.kernel.org,
	vgoyal@...ibm.com, ak@....de, fastboot@...ts.osdl.org,
	anderson@...hat.com
Subject: Re: [PATCH 02/02] Elf: Align elf notes properly

From: Jeremy Fitzhardinge <jeremy@...p.org>
Date: Fri, 10 Nov 2006 15:37:19 -0800

> Magnus Damm wrote:
> > I see no point in aligning to 32-bit boundaries on 64-bit platforms.
> > Their intention was most likely to align to the word size IMO, so this
> > is most likely a "thinko" left over from whoever ported the code from
> > 32-bit to 64-bit.
> 
> I don't think so.  Since Elf64 notes still have 32-bit values in them,
> 32-bit alignment seems the most sensible.  It would certainly be an
> irritation to have Elf32 and Elf64 Notes with basically the same
> definition, but with different alignments.

I think Elf64 notes very much would need 64-bit alignment, especially
if there are u64 objects in there.  Otherwise it would not be possible
to directly dereference such objects without taking unaligned faults
on several types of RISC cpus.

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