Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933297AbbELP0U (ORCPT ); Tue, 12 May 2015 11:26:20 -0400 Received: from mail-wi0-f169.google.com ([209.85.212.169]:35473 "EHLO mail-wi0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932718AbbELP0A (ORCPT ); Tue, 12 May 2015 11:26:00 -0400 MIME-Version: 1.0 In-Reply-To: References: <1431387505-13410-1-git-send-email-alexhenrie24@gmail.com> <20150512064032.GA25097@gmail.com> Date: Tue, 12 May 2015 08:25:59 -0700 Message-ID: Subject: Re: [PATCH v2] x86: Preserve iopl on fork and execve From: Arjan van de Ven To: Ingo Molnar Cc: Alex Henrie , One Thousand Gnomes , Kees Cook , "H . Peter Anvin" , Doug Johnson , Thomas Gleixner , Ingo Molnar , Tyler Hicks , Al Viro , LKML , Andy Lutomirski , Linus Torvalds , Andrew Morton , Borislav Petkov , Peter Zijlstra , Arjan van de Ven , Denys Vlasenko , Brian Gerst Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 700 Lines: 16 > > also the interesting question is: > can a process give up these perms? > otherwise it becomes a "once given, never gotten rid of" hell hole. If you look at a modern linux distro, nothing should need/use iopl and co anymore, so maybe an interesting question is if we can stick these behind a CONFIG_ option (default on of course for compatibility)... just like some of the /dev/mem like things are now hidable for folks who know they don't need them. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/