linux-kernel - RE: [patch 1/2] Relocate VDSO ELF headers to match mapped location with COMPAT

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: <8646EB4D6B054F4E8AB083CA829C4C810107364E@iddrintx1.iddri.chevrontexaco.net>
Date:	Thu, 5 Apr 2007 14:45:56 +0700
From:	"Raharjo, Cahyo \(cahr\)" <Cahyo.Raharjo@...vron.com>
To:	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	"Jan Beulich" <jbeulich@...ell.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	<virtualization@...ts.osdl.org>,
	"Roland McGrath" <roland@...hat.com>, "Andi Kleen" <ak@...e.de>,
	"lkml" <linux-kernel@...r.kernel.org>,
	"Zachary Amsden" <zach@...are.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: RE: [patch 1/2] Relocate VDSO ELF headers to match mapped	location with COMPAT_VDSO

Dear All,
In this few days, I got emails from this list. I tried to exclude thru
majordomo, but it failed.
Kindly need your help to exclude me from this list.


Thank You, 
CR


-----Original Message-----
From: linux-kernel-owner@...r.kernel.org
[mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of Jeremy
Fitzhardinge
Sent: Thursday, April 05, 2007 2:32 PM
To: Jan Beulich
Cc: Ingo Molnar; Andrew Morton; virtualization@...ts.osdl.org; Roland
McGrath; Andi Kleen; lkml; Zachary Amsden; Eric W. Biederman
Subject: Re: [patch 1/2] Relocate VDSO ELF headers to match mapped
location with COMPAT_VDSO

Jan Beulich wrote:
> While there's a certain level of control on what DT_* may appear in 
> the vDSO, not even considering other than the above types seems 
> fragile to me. Since future additions to the set are supposedly 
> following a fixed scheme (distinguishing pointers and values via the 
> low bit when below OLD_DT_LOOS, and using sub-ranges when between 
> DT_HIOS and OLD_DT_HIOS), at least also handling those would seem like

> a good idea, as would warning about unrecognized types.
>   

I wasn't aware of this scheme.  Where is it documented?

> Also, even though it shouldn't matter for the final result, if doing 
> things spec-conforming here you should use d_un.d_ptr.
>   

Yes, I've already fixed that.

> In addition to Roland's remarks about missing symbol table relocation,

> I would also assume section headers, if present, should be relocated.
>   

Yes, I suppose that's easy enough to add.

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