linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Kill some chicken bits
Date: Wed, 21 Oct 2015 01:09:12 -0700	[thread overview]
Message-ID: <56274828.6020909@zytor.com> (raw)
In-Reply-To: <20151020170457.GF31130@pd.tnic>

On 10/20/2015 10:04 AM, Borislav Petkov wrote:
> 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...
> 

Some chicken bits may be better than others, though.

	-hpa


      reply	other threads:[~2015-10-21  8:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 16:33 [PATCH] x86: Kill some chicken bits Borislav Petkov
2015-10-20 16:58 ` H. Peter Anvin
2015-10-20 17:04   ` Borislav Petkov
2015-10-21  8:09     ` H. Peter Anvin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56274828.6020909@zytor.com \
    --to=hpa@zytor.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).