linux-kernel - Re: [2.6.25] compat VDSO option not disabling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4816029D.3030508@goop.org>
Date:	Mon, 28 Apr 2008 10:00:13 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Gerhard Mack <gmack@...erfire.net>
CC:	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: [2.6.25] compat VDSO option not disabling

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/