All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: virtualization@lists.osdl.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
	Roland McGrath <roland@redhat.com>
Subject: Re: [patch 1/2] Relocate VDSO ELF headers to match mapped	location with COMPAT_VDSO
Date: Thu, 05 Apr 2007 00:31:38 -0700	[thread overview]
Message-ID: <4614A5DA.9050700@goop.org> (raw)
In-Reply-To: <4614BD10.76E4.0078.0@novell.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	virtualization@lists.osdl.org, Roland McGrath <roland@redhat.com>,
	Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>,
	Zachary Amsden <zach@vmware.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [patch 1/2] Relocate VDSO ELF headers to match mapped	location with COMPAT_VDSO
Date: Thu, 05 Apr 2007 00:31:38 -0700	[thread overview]
Message-ID: <4614A5DA.9050700@goop.org> (raw)
In-Reply-To: <4614BD10.76E4.0078.0@novell.com>

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

  reply	other threads:[~2007-04-05  7:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05  4:58 [patch 0/2] Updates to compat VDSOs Jeremy Fitzhardinge
2007-04-05  4:58 ` [patch 1/2] Relocate VDSO ELF headers to match mapped location with COMPAT_VDSO Jeremy Fitzhardinge
2007-04-05  6:31   ` Roland McGrath
2007-04-05  6:31     ` Roland McGrath
2007-04-05  6:46     ` Jeremy Fitzhardinge
2007-04-05  8:14       ` Roland McGrath
2007-04-05  8:14         ` Roland McGrath
2007-04-05  7:10   ` Jan Beulich
2007-04-05  7:10     ` Jan Beulich
2007-04-05  7:31     ` Jeremy Fitzhardinge [this message]
2007-04-05  7:31       ` Jeremy Fitzhardinge
2007-04-05  7:45       ` Raharjo, Cahyo (cahr)
2007-04-05  7:45         ` Raharjo, Cahyo (cahr)
2007-04-05  7:47       ` Jan Beulich
2007-04-05  7:47         ` Jan Beulich
2007-04-05  8:14     ` Roland McGrath
2007-04-05  8:14       ` Roland McGrath
2007-04-05  8:18       ` Jeremy Fitzhardinge
2007-04-05  8:54         ` Jan Beulich
2007-04-05  8:54           ` Jan Beulich
2007-04-05  8:58         ` Roland McGrath
2007-04-05  4:58 ` [patch 2/2] Make COMPAT_VDSO runtime selectable Jeremy Fitzhardinge
  -- strict thread matches above, loose matches on Subject: below --
2007-04-05 15:53 [patch 0/2] Updates to compat VDSOs Jeremy Fitzhardinge
2007-04-05 15:53 ` [patch 1/2] Relocate VDSO ELF headers to match mapped location with COMPAT_VDSO Jeremy Fitzhardinge
2007-04-05 15:53   ` Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4614A5DA.9050700@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    --cc=virtualization@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.