linux-kernel - Re: [RFC v2] x86-64: Allow emulated vsyscalls from user addresses

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]

Date:	Sun, 7 Aug 2011 17:44:56 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Andrew Lutomirski <luto@....edu>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Andi Kleen <andi@...stfloor.org>, x86@...nel.org,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	lueckintel@...oo.com, kimwooyoung@...il.com,
	Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: [RFC v2] x86-64: Allow emulated vsyscalls from user addresses

On Sun, Aug 07, 2011 at 08:58:56AM -0400, Andrew Lutomirski wrote:
> > Also, what do we do with userspace which decides to hardcode "int 0x4[012]"
> > somewhere in the meantime?
> 
> Break it?  Any code that does that will get an unconditional warning
> with this patch.

Ok, I hope you're right. Because I'm sure you remember the last
prominent time the kernel broke userspace in the face of powertop.
Although having the warning should be fine, i.e. along the lines of "you
silly userspace process have been warned."

Thanks.

-- 
Regards/Gruss,
    Boris.
--
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/