From: "Jan Beulich" <jbeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
xen-devel@lists.xensource.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/10] linux 2.6.18: COMPAT_VDSO
Date: Tue, 06 Mar 2007 07:52:47 +0000 [thread overview]
Message-ID: <45ED2BDF.76E4.0078.0@novell.com> (raw)
In-Reply-To: <45EC787B.2020807@goop.org>
>Ingo just raised this as an issue for paravirt_ops as well. I don't
>quite follow what's going on there. My understanding is that there are
>some old versions of glibc (which were unreleased CVS snapshots shipped
>by some vendors) which don't use the vdso's ELF header, but instead have
>their own canned one which built into the library itself.
Perhaps you meanwhile saw the similar question from Keir regarding this
(and my answer), but in short: plain glibc 2.3.2 (at least) supports AT_SYSINFO
but not AT_SYSINFO_HDR. In this scenario, moving the vDSO around is fine,
but glibc-internal (arguably broken) consistency checks prevent the vDSO from
being accepted when not using COMPAT_VDSO.
Jan
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <jbeulich@novell.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Virtualization Mailing List" <virtualization@lists.osdl.org>,
<xen-devel@lists.xensource.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Andi Kleen" <ak@suse.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/10] linux 2.6.18: COMPAT_VDSO
Date: Tue, 06 Mar 2007 07:52:47 +0000 [thread overview]
Message-ID: <45ED2BDF.76E4.0078.0@novell.com> (raw)
In-Reply-To: <45EC787B.2020807@goop.org>
>Ingo just raised this as an issue for paravirt_ops as well. I don't
>quite follow what's going on there. My understanding is that there are
>some old versions of glibc (which were unreleased CVS snapshots shipped
>by some vendors) which don't use the vdso's ELF header, but instead have
>their own canned one which built into the library itself.
Perhaps you meanwhile saw the similar question from Keir regarding this
(and my answer), but in short: plain glibc 2.3.2 (at least) supports AT_SYSINFO
but not AT_SYSINFO_HDR. In this scenario, moving the vDSO around is fine,
but glibc-internal (arguably broken) consistency checks prevent the vDSO from
being accepted when not using COMPAT_VDSO.
Jan
next prev parent reply other threads:[~2007-03-06 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 11:14 [PATCH 2/10] linux 2.6.18: COMPAT_VDSO Jan Beulich
2007-03-05 13:42 ` Keir Fraser
2007-03-05 14:48 ` Jan Beulich
2007-03-05 15:55 ` Keir Fraser
2007-03-09 10:17 ` Jan Beulich
2007-03-09 10:39 ` Keir Fraser
2007-03-09 14:59 ` Jeremy Fitzhardinge
2007-03-05 20:07 ` Jeremy Fitzhardinge
2007-03-05 20:07 ` [Xen-devel] " Jeremy Fitzhardinge
2007-03-06 7:52 ` Jan Beulich [this message]
2007-03-06 7:52 ` Jan Beulich
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=45ED2BDF.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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 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.