mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: Jiang Biao <jiang.biao2@zte.com.cn>,
	tglx@linutronix.de, mingo@redhat.com
Cc: luto@kernel.org, hpa@zytor.com, x86@kernel.org,
	albcamus@gmail.com, linux-kernel@vger.kernel.org,
	zhong.weidong@zte.com.cn
Subject: Re: [PATCH 4/5] x86/pti: warn for unknown pti boot options
Date: Mon, 16 Jul 2018 07:34:53 -0700	[thread overview]
Message-ID: <e9d8602d-bf6b-dff2-5cfa-ab6278e2f771@linux.intel.com> (raw)
In-Reply-To: <1531713820-24544-5-git-send-email-jiang.biao2@zte.com.cn>

On 07/15/2018 09:03 PM, Jiang Biao wrote:
> When using unknown pti boot options other than on/off/auto, we
> select auto silently, which is sometimes confusing. Add warning for
> unknown pti boot options like we do in
> spectre_v2_select_mitigation().

There's not a lot of precedent for this one.  We have gazillions of boot
options and I don't know of many places that we do this.  While this
isn't a horrible idea, I don't look forward to the patches will do this
for every other option in the kernel.

  reply	other threads:[~2018-07-16 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16  4:03 [PATCH 0/5] x86/pti: small fixes and cleanups for pti Jiang Biao
2018-07-16  4:03 ` [PATCH 1/5] x86/pti: check the return value of pti_user_pagetable_walk_p4d Jiang Biao
2018-07-16 14:28   ` Dave Hansen
2018-07-16  4:03 ` [PATCH 2/5] x86/pti: check the return value of pti_user_pagetable_walk_pmd Jiang Biao
2018-07-16  4:03 ` [PATCH 3/5] x86/pti: make pti_set_kernel_image_nonglobal static Jiang Biao
2018-07-16 15:16   ` Dave Hansen
2018-07-16 16:04   ` [tip:x86/pti] x86/pti: Make pti_set_kernel_image_nonglobal() static tip-bot for Jiang Biao
2018-07-16  4:03 ` [PATCH 4/5] x86/pti: warn for unknown pti boot options Jiang Biao
2018-07-16 14:34   ` Dave Hansen [this message]
2018-07-16  4:03 ` [PATCH 5/5] x86/pti: constify address parameters Jiang Biao
2018-07-16 14:37   ` Dave Hansen

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=e9d8602d-bf6b-dff2-5cfa-ab6278e2f771@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --cc=albcamus@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jiang.biao2@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=zhong.weidong@zte.com.cn \
    /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
Powered by JetHome