From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752266AbbJTRFB (ORCPT ); Tue, 20 Oct 2015 13:05:01 -0400 Received: from mail.skyhub.de ([78.46.96.112]:55343 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750910AbbJTRFA (ORCPT ); Tue, 20 Oct 2015 13:05:00 -0400 Date: Tue, 20 Oct 2015 19:04:57 +0200 From: Borislav Petkov To: "H. Peter Anvin" Cc: X86 ML , LKML Subject: Re: [PATCH] x86: Kill some chicken bits Message-ID: <20151020170457.GF31130@pd.tnic> References: <1445358810-12800-1-git-send-email-bp@alien8.de> <90D1893E-1143-4B81-B849-74EB8B27574F@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <90D1893E-1143-4B81-B849-74EB8B27574F@zytor.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 20, 2015 at 09:58:18AM -0700, H. Peter Anvin wrote: > I would like to keep nosmap until SMAP hardware is more ubiquitous > since SMAP is vulnerable to kernel bugs. We have already had a case > where a maintainer pushed "cleanup" code straight to Linus, bypassing > the x86 maintainers, which broke booting on SMAP hardware. Right, so the thought came to my mind while going through those, that we don't really know what they're going to be good for and what we're going to need them for in the future. So maybe we want to keep them after all - you never know. For example, luto made me use "nosep" recently even though that's an ancient chicken bit. So maybe we want to not remove them ever - the cleanup win is not that great to even care... -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.