mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefani Seibold <stefani@seibold.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@amacapital.net>, X86 ML <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Fix the symbol versions on the 32-bit vDSO
Date: Sun, 30 Mar 2014 21:00:40 +0200	[thread overview]
Message-ID: <1396206040.9781.1.camel@vger.seibold.net> (raw)
In-Reply-To: <70a0dc4b-14d4-4684-9da8-b162a0303c17@email.android.com>

I think it is in review. I still wait for the confirmation of my assign
form.

Am Sonntag, den 30.03.2014, 09:59 -0700 schrieb H. Peter Anvin:
> Has your glibc patch been accepted upstream yet? I'm assuming not, in which case this is a legitimate patch.
> 
> On March 29, 2014 11:33:37 PM PDT, Stefani Seibold <stefani@seibold.net> wrote:
> >Am Samstag, den 29.03.2014, 13:15 -0700 schrieb Andy Lutomirski:
> >> The new symbols provide the same API as the 64-bit variants, so they
> >> should have the same symbol version name.  This can't break
> >> userspace, since these symbols are new for 32-bit Linux.
> >> 
> >
> >This breaks my glibc patch... What is the benefit for doing this in
> >that
> >way?
> >
> >> Signed-off-by: Andy Lutomirski <luto@amacapital.net>
> >> ---
> >>  arch/x86/vdso/vdso32/vdso32.lds.S | 10 +++++++---
> >>  1 file changed, 7 insertions(+), 3 deletions(-)
> >> 
> >> diff --git a/arch/x86/vdso/vdso32/vdso32.lds.S
> >b/arch/x86/vdso/vdso32/vdso32.lds.S
> >> index 28c4607..aadb8b9 100644
> >> --- a/arch/x86/vdso/vdso32/vdso32.lds.S
> >> +++ b/arch/x86/vdso/vdso32/vdso32.lds.S
> >> @@ -23,14 +23,18 @@ ENTRY(__kernel_vsyscall);
> >>   */
> >>  VERSION
> >>  {
> >> +	LINUX_2.6 {
> >> +	global:
> >> +		__vdso_clock_gettime;
> >> +		__vdso_gettimeofday;
> >> +		__vdso_time;
> >> +	};
> >> +
> >>  	LINUX_2.5 {
> >>  	global:
> >>  		__kernel_vsyscall;
> >>  		__kernel_sigreturn;
> >>  		__kernel_rt_sigreturn;
> >> -		__vdso_clock_gettime;
> >> -		__vdso_gettimeofday;
> >> -		__vdso_time;
> >>  	local: *;
> >>  	};
> >>  }
> 



  reply	other threads:[~2014-03-30 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 20:15 Andy Lutomirski
2014-03-30  6:33 ` Stefani Seibold
2014-03-30  6:49   ` Andy Lutomirski
2014-03-30 16:59   ` H. Peter Anvin
2014-03-30 19:00     ` Stefani Seibold [this message]
2014-03-30 19:09       ` H. Peter Anvin
2014-03-30 17:28 ` [tip:x86/vdso] x86, vdso: " tip-bot for Andy Lutomirski

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=1396206040.9781.1.camel@vger.seibold.net \
    --to=stefani@seibold.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®