From: Marc Zyngier <maz@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, arnd@arndb.de, sashal@kernel.org,
naresh.kamboju@linaro.org, Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [Stable-5.4][PATCH 0/3] arm64: Allow the compat vdso to be disabled at runtime
Date: Fri, 17 Jul 2020 09:02:06 +0100 [thread overview]
Message-ID: <c9f5b2b0512067b128dd5c98acc5db7e@kernel.org> (raw)
In-Reply-To: <20200716115813.GB1668009@kroah.com>
Hi Greg,
On 2020-07-16 12:58, Greg KH wrote:
> On Wed, Jul 15, 2020 at 01:56:11PM +0100, Marc Zyngier wrote:
>> This is a backport of the series that recently went into 5.8. Note
>> that the first patch is more a complete rewriting than a backport, as
>> the vdso implementation in 5.4 doesn't have much in common with
>> mainline. This affects the 32bit arch code in a benign way.
>>
>> It has seen very little testing, as I don't have the HW that triggers
>> this issue. I have run it in VMs by faking the CPU MIDR, and nothing
>> caught fire. Famous last words.
>
> These are also needed in 5.7.y, right? If so, I need that series
> before
> I can take this one as we don't want people moving to a newer kernel
> and
> suffer regressions :(
The original mainline changes:
4b661d6133c5 arm64: arch_timer: Disable the compat vdso for cores
affected by ARM64_WORKAROUND_1418040
c1fbec4ac0d7 arm64: arch_timer: Allow an workaround descriptor to
disable compat vdso
97884ca8c292 arm64: Introduce a way to disable the 32bit vdso
do apply cleanly to stable-5.7. Do you want me to resend them
separately,
or will you pick the patches directly from mainline?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-07-17 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:56 [Stable-5.4][PATCH 0/3] arm64: Allow the compat vdso to be disabled at runtime Marc Zyngier
2020-07-15 12:56 ` [Stable-5.4][PATCH 1/3] arm64: Introduce a way to disable the 32bit vdso Marc Zyngier
2020-07-15 12:56 ` [Stable-5.4][PATCH 2/3] arm64: arch_timer: Allow an workaround descriptor to disable compat vdso Marc Zyngier
2020-07-15 12:56 ` [Stable-5.4][PATCH 3/3] arm64: arch_timer: Disable the compat vdso for cores affected by ARM64_WORKAROUND_1418040 Marc Zyngier
2020-07-16 11:58 ` [Stable-5.4][PATCH 0/3] arm64: Allow the compat vdso to be disabled at runtime Greg KH
2020-07-17 8:02 ` Marc Zyngier [this message]
2020-07-17 9:33 ` Greg KH
2020-07-17 9: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=c9f5b2b0512067b128dd5c98acc5db7e@kernel.org \
--to=maz@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).