Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org D09AA60F72
MIME-Version: 1.0
In-Reply-To: <1518616386206238@kroah.com>
References: <1518616386206238@kroah.com>
From:   Timur Tabi <timur@codeaurora.org>
Date:   Wed, 14 Feb 2018 10:16:51 -0600
Message-ID: <CAOZdJXWZV4TDZchsYeHE_Oh+s1y3yjXE9NxVY9wz-vCkZVhN4w@mail.gmail.com>
Subject: Re: Patch "[Variant 2/Spectre-v2] arm64: Implement branch predictor
 hardening for Falkor" has been added to the 4.14-stable tree
To:     lkml <linux-kernel@vger.kernel.org>
Cc:     Shanker Donthineni <shankerd@codeaurora.org>,
        Ard Biesheuvel <ard.biesheuvel@linaro.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Will Deacon <will.deacon@arm.com>, stable@vger.kernel.org,
        stable-commits@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Feb 14, 2018 at 7:53 AM,  <gregkh@linuxfoundation.org> wrote:
>
> This is a note to let you know that I've just added the patch titled
>
>     [Variant 2/Spectre-v2] arm64: Implement branch predictor hardening for Falkor
>
> to the 4.14-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
>      arm64-implement-branch-predictor-hardening-for-falkor.patch
> and it can be found in the queue-4.14 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.

Please note that there is a follow-on patch, also from Shanker, that
fixes this patch (it was slightly mangled when merged into 4.16-rc1):

https://www.spinics.net/lists/arm-kernel/msg633726.html

I would love for it to be included in 4.14.20, but it hasn't been
merged into Linus' tree yet.  I will send a patch request when it does
land in 4.16-rc2.