From: Greg KH <gregkh@linuxfoundation.org>
To: Diana Craciun <diana.craciun@nxp.com>
Cc: linuxppc-dev@ozlabs.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 stable v4.4 2/2] Documentation: Add nospectre_v1 parameter
Date: Tue, 30 Apr 2019 15:25:23 +0200 [thread overview]
Message-ID: <20190430132523.GB5327@kroah.com> (raw)
In-Reply-To: <1556628147-15687-2-git-send-email-diana.craciun@nxp.com>
On Tue, Apr 30, 2019 at 03:42:27PM +0300, Diana Craciun wrote:
> commit 26cb1f36c43ee6e89d2a9f48a5a7500d5248f836 upstream.
>
> Currently only supported on powerpc.
>
> Signed-off-by: Diana Craciun <diana.craciun@nxp.com>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
> Documentation/kernel-parameters.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index f0bdf78420a0..3ff87d5d6fea 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -2449,6 +2449,10 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> legacy floating-point registers on task switch.
>
> nohugeiomap [KNL,x86] Disable kernel huge I/O mappings.
> +
> + nospectre_v1 [PPC] Disable mitigations for Spectre Variant 1 (bounds
> + check bypass). With this option data leaks are possible
> + in the system.
>
> nospectre_v2 [X86,PPC_FSL_BOOK3E] Disable all mitigations for the Spectre variant 2
> (indirect branch prediction) vulnerability. System may
> --
> 2.17.1
>
Both of these patches needed to be added to a bunch of the stable trees,
so I've now done that.
thanks,
greg k-h
prev parent reply other threads:[~2019-04-30 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 12:42 [PATCH v2 stable v4.4 1/2] powerpc/fsl: Add FSL_PPC_BOOK3E as supported arch for nospectre_v2 boot arg Diana Craciun
2019-04-30 12:42 ` [PATCH v2 stable v4.4 2/2] Documentation: Add nospectre_v1 parameter Diana Craciun
2019-04-30 13:23 ` Greg KH
2019-04-30 13:25 ` Greg KH [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=20190430132523.GB5327@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=diana.craciun@nxp.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=stable@vger.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