[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200716115813.GB1668009@kroah.com>
Date: Thu, 16 Jul 2020 13:58:13 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Marc Zyngier <maz@...nel.org>
Cc: stable@...r.kernel.org, arnd@...db.de, sashal@...nel.org,
naresh.kamboju@...aro.org, Mark Rutland <mark.rutland@....com>,
Will Deacon <will@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Russell King <linux@....linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [Stable-5.4][PATCH 0/3] arm64: Allow the compat vdso to be
disabled at runtime
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 :(
thanks,
greg k-h
Powered by blists - more mailing lists