linux-kernel - Re: [PATCH 1 of 1] x86_64: Put .note.* sections into a PT

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: <44EB1E9E.5030307@goop.org>
Date:	Tue, 22 Aug 2006 08:11:26 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ian Campbell <Ian.Campbell@...source.com>
CC:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...l.org>,
	Ian Pratt <ian.pratt@...source.com>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	Chris Wright <chrisw@...s-sol.org>,
	Virtualization <virtualization@...ts.osdl.org>,
	Christoph Lameter <clameter@....com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH 1 of 1] x86_64: Put .note.* sections into a PT_NOTE segment
 in vmlinux

Ian Campbell wrote:
> It has been suggested to me that the notes segment should have flags 0
> (i.e. not readable) since it is only used by the loader and is not used
> at runtime. For now I went with a readable segment since that is what
> the i386 patch uses.
>   

Note that the PT_NOTEs segment is aliased to a part of one of the 
PT_LOADs - ie, it points into the data segment.  So making it -rwx would 
either be ignored, or also require putting the bits into a new PT_LOAD 
segment with 0 permissions, which is pretty pointless.  I made it R_E 
just so there was no permissions conflict, though the _E part could 
probably go.

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