From: Greg KH <gregkh@linuxfoundation.org>
To: Will Deacon <will@kernel.org>
Cc: stable@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG}
Date: Wed, 7 Aug 2019 17:52:29 +0200 [thread overview]
Message-ID: <20190807155229.GA27143@kroah.com> (raw)
In-Reply-To: <20190805171410.19358-1-will@kernel.org>
On Mon, Aug 05, 2019 at 06:14:10PM +0100, Will Deacon wrote:
> commit 147b9635e6347104b91f48ca9dca61eb0fbf2a54 upstream.
>
> If CTR_EL0.{CWG,ERG} are 0b0000 then they must be interpreted to have
> their architecturally maximum values, which defeats the use of
> FTR_HIGHER_SAFE when sanitising CPU ID registers on heterogeneous
> machines.
>
> Introduce FTR_HIGHER_OR_ZERO_SAFE so that these fields effectively
> saturate at zero.
>
> Fixes: 3c739b571084 ("arm64: Keep track of CPU feature registers")
> Cc: <stable@vger.kernel.org> # 4.14.y only
> Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Will Deacon <will@kernel.org>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
>
> Backport for 4.14.y -stable kernel, after original failed to apply:
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2019-08-07 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 17:14 [PATCH] arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG} Will Deacon
2019-08-07 15:52 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-30 14:40 [PATCH] arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG, ERG} Will Deacon
2019-07-30 14:45 ` [PATCH] arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG} Suzuki K Poulose
2019-07-30 16:53 ` [PATCH] arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG, ERG} Mark Rutland
2019-07-31 17:11 ` [PATCH] arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG} Catalin Marinas
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=20190807155229.GA27143@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=stable@vger.kernel.org \
--cc=will@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 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.