linux-kernel - Re: [PATCH] x86: vm86 - hide X86_VM

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] [day] [month] [year] [list]

Message-ID: <20080429174412.GF6837@cvg>
Date:	Tue, 29 Apr 2008 21:44:12 +0400
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>, David Woodhouse <dwmw2@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86: vm86 - hide X86_VM_MASK from userland programs v2

[H. Peter Anvin - Tue, Apr 29, 2008 at 08:46:09AM -0700]
> Cyrill Gorcunov wrote:
>> | | with this patch we have <asm/vm86.h> included only
>> | if __i386__ defined *BUT* X86_VM_MASK is tried to be
>> | used *without* __386__ being checked (as example - 
>> ptrace.h:user_mode_vm).
>> | I'm not sure how to properly hanle this situation. But will take a look.
>> | | So I suggest you drop my last patch (which moves X86_VM_MASK
>> | into __KERNEL__ section) for a while. I'll recheck all
>> | this stuff later (too busy now).
>> | | 		- Cyrill -
>> Thomas, could you take a look please - is my suspicious wrong?
>> 		- Cyrill -
>
> X86_VM_MASK should be defined to zero on x86-64.  Part of the reason for 
> this symbol is so we don't have to put #ifdef around its uses.
>
> 	-hpa
>

Thanks Ingo for report - all just became clear - I've tried to define
tese flags *after* ptrace.h inclusion - will fix ASAP.

		- Cyrill -
--
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/