All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: john.blackwood@ccur.com, linux-kernel@vger.kernel.org,
	Jeremy Fitzhardinge <jeremy@xensource.com>,
	Roland McGrath <roland@redhat.com>,
	bugsy@ccur.com, Andrew Morton <akpm@linux-foundation.org>,
	Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH] Reading the VDSO area - i386
Date: Tue, 17 Jul 2007 10:51:58 -0700	[thread overview]
Message-ID: <469D01BE.7070204@goop.org> (raw)
In-Reply-To: <200707171948.42054.ak@suse.de>

Andi Kleen wrote:
> On Tuesday 17 July 2007 18:47:56 Jeremy Fitzhardinge wrote:
>   
>> John Blackwood wrote:
>>     
>>> I was doing some tests that attempt to read the VDSO area of a
>>> task through either the /proc/pid/mem or ptrace(PTRACE_PEEKTEXT,
>>> ...) interfaces, and it seems that when the CONFIG_COMPAT_VDSO kernel
>>> parameter is enabled, we can no longer successfully read the VDSO area
>>> on i386 kernels.
>>>       
>> Thanks.  Someone else noticed this recently, and posted a near-identical
>> patch.  But I can't seem to find it right now...
>>
>> Andrew, Andi: do you remember something like this passing by?
>>     
>
> Yes it was from Jan Beulich.
>   

Ah, yes.  For some reason I can't find it in my archives.  Do you have
it queued up?

    J


  reply	other threads:[~2007-07-17 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 16:23 [PATCH] Reading the VDSO area - i386 John Blackwood
2007-07-17 16:47 ` Jeremy Fitzhardinge
2007-07-17 17:48   ` Andi Kleen
2007-07-17 17:51     ` Jeremy Fitzhardinge [this message]
2007-07-17 17:57       ` Andi Kleen

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=469D01BE.7070204@goop.org \
    --to=jeremy@goop.org \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=bugsy@ccur.com \
    --cc=jbeulich@novell.com \
    --cc=jeremy@xensource.com \
    --cc=john.blackwood@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.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.