From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Roland McGrath <roland@redhat.com>
Cc: Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
virtualization@lists.osdl.org,
lkml <linux-kernel@vger.kernel.org>,
Zachary Amsden <zach@vmware.com>,
Jan Beulich <JBeulich@novell.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 1/2] Relocate VDSO ELF headers to match mapped location with COMPAT_VDSO
Date: Wed, 04 Apr 2007 23:46:29 -0700 [thread overview]
Message-ID: <46149B45.2070502@goop.org> (raw)
In-Reply-To: <20070405063152.9227D180064@magilla.sf.frob.com>
Roland McGrath wrote:
> The patch looks nice and clean. However, it does not relocate the symbol
> table(s) values. I thought that was done in an earlier version of this I
> saw, but I might be misremembering. Though not fatal, this is a regression
> from the previous CONFIG_COMPAT_VDSO behavior. It will show up in things
> like __kernel_* name display in backtraces.
Hm, OK. It does, but I wasn't sure if it would matter. It should be
fairly simple to fix up.
> If with your other patch
> CONFIG_COMPAT_VDSO will become other than a rarely-used compatibility
> option, then this should be fixed. Note that with your second patch this
> will also break the symbol values in the randomly-located vma vdso;
> non-ancient glibc doesn't care if the vdso isn't mapped where its phdrs
> say, but everything does still care that the symbol tables in an ELF file
> use addresses matching the phdrs in the same file.
>
I did the second patch because I could, and to see if it would provoke
some comment. But effectively removing a kernel config option seems
like a good idea to me.
J
next prev parent reply other threads:[~2007-04-05 6:46 UTC|newest]
Thread overview: 15+ 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:46 ` Jeremy Fitzhardinge [this message]
2007-04-05 8:14 ` Roland McGrath
2007-04-05 7:10 ` Jan Beulich
2007-04-05 7:31 ` Jeremy Fitzhardinge
2007-04-05 7:45 ` Raharjo, Cahyo (cahr)
2007-04-05 7:47 ` Jan Beulich
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: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
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=46149B45.2070502@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).