public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Gerhard Mack <gmack@innerfire.net>
Cc: Jiri Kosina <jkosina@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.25] compat VDSO option not disabling
Date: Mon, 28 Apr 2008 10:00:13 -0700	[thread overview]
Message-ID: <4816029D.3030508@goop.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0804281145090.17060@mtl.rackplans.net>

Gerhard Mack wrote:
> On Sat, 26 Apr 2008, Jeremy Fitzhardinge wrote:
>   
>> Gerhard Mack wrote:
>>     
>>> I havn't enabled compat VDSO at the kernel command line or otherwise.
>>> Something broke with this option.   
>>>       
>> Yes, you might be on to something.  I think I've been seeing that message when
>> I wouldn't expect to.  I'll double-check.  Could you send your complete dmesg
>> output?
>>
>>     
> Of course
>
>
> Compat vDSO mapped to ffffe000.
>   

I think this is just a false alarm.  sysenter_setup always prints this, 
but if compat mode isn't enabled this is just the address the compat 
vdso would be at if it were mapped.  You can confirm this by doing "cat 
/proc/self/maps" and making sure that there's nothing mapped at 
ffffe000.  And then cross confirm with "sysctl -w vm.vdso_enabled=2; cat 
/proc/self/maps" to make sure it appears.

    J

  reply	other threads:[~2008-04-28 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 16:49 [2.6.25] compat VDSO option not disabling Gerhard Mack
2008-04-25 14:33 ` Jiri Kosina
2008-04-26 16:15   ` Gerhard Mack
2008-04-27  5:10     ` Jeremy Fitzhardinge
2008-04-28 15:46       ` Gerhard Mack
2008-04-28 17:00         ` Jeremy Fitzhardinge [this message]
2008-04-28 17:24           ` Gerhard Mack
2008-04-28 18:05             ` [PATCH] x86: don't bother printing compat vdso address Jeremy Fitzhardinge
2008-04-29 10:01               ` Ingo Molnar

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=4816029D.3030508@goop.org \
    --to=jeremy@goop.org \
    --cc=gmack@innerfire.net \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.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