All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Will Deacon <will.deacon@arm.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	ard.biesheuvel@linaro.org
Subject: Re: [GIT PULL] arm64 spectre and meltdown mitigations for -stable
Date: Fri, 9 Feb 2018 14:49:57 +0100	[thread overview]
Message-ID: <20180209134957.GA1677@kroah.com> (raw)
In-Reply-To: <20180209134811.GB11309@arm.com>

On Fri, Feb 09, 2018 at 01:48:11PM +0000, Will Deacon wrote:
> Hi Greg,
> 
> I've put together a tag which includes all of the upstream arm64 spectre and
> meltdown mitigations based on v4.15. Please could you consider taking this
> into the 4.15 stable tree?
> 
> I understand that Ard (cc'd) is using this stack to create a version for 4.14
> too.
> 
> Note that there are two commits in here that are already in stable:
> 
>   9c9345fb26ff [Variant 1/Spectre-v1] Documentation: Document array_index_nospec
>   60d6c8a8e54e [Variant 1/Spectre-v1] array_index_nospec: Sanitize speculative array de-references
> 
> so you can skip those when applying.
> 
> Please shout if you run into trouble.

Ah, nice, thanks for this.  I'll use this for the next 4.15.y kernel
release after the one I _just_ sent out for review a few minutes ago.

greg k-h

  reply	other threads:[~2018-02-09 13:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 13:48 [GIT PULL] arm64 spectre and meltdown mitigations for -stable Will Deacon
2018-02-09 13:49 ` Greg KH [this message]
2018-02-09 13:51   ` Will Deacon
2018-02-09 15:04     ` Greg KH
2018-02-13 16:48       ` Greg KH
2018-02-14 12:41         ` Will Deacon
2018-02-14 12:54           ` Greg KH
2018-02-14 13:56             ` Greg KH
2018-02-21 12:53 ` Greg KH
2018-02-21 13:43   ` Ard Biesheuvel
2018-02-21 13:47     ` Greg KH

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=20180209134957.GA1677@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.