Re: [GIT PULL v2] KVM/arm64 fixes for 6.3, part #4

[Marc Zyngier <maz@kernel.org>]

On Sat, 22 Apr 2023 19:35:35 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
> 
> On Sat, Apr 22, 2023 at 10:05:38AM +0100, Marc Zyngier wrote:
> > On 2023-04-22 00:51, Paolo Bonzini wrote:
> > > On 4/19/23 17:54, Oliver Upton wrote:
> > > > Hi Paolo,
> > > > 
> > > > Here is v2 of the last batch of fixes for 6.3 (for real this time!)
> > > > 
> > > > Details in the tag, but the noteworthy addition is Dan's fix for a
> > > > rather obvious buffer overflow when writing to a firmware register.
> > > 
> > > At least going by the Fixes tag, I think this one should have been
> > > Cc'd to stable as well.  Can you send it next week or would you like
> > > someone else to handle the backport?
> 
> Thanks for spotting that, I had a mental note to do so, but my memory is
> fleeting at best :)
> 
> > Indeed, that's missing. But yes, backports are definitely on
> > the cards, and we'll make sure all stable versions get fixed
> > as soon as the fix hits Linus' tree.
> 
> Between this last batch of fixes for 6.3 and the 6.4 pull we've accrued
> quite a backlog of stable-worthy patches, many of them are likely to be
> nontrivial backports.
> 
> I'll do the config_lock series, and I can pick up the firmware reg fix
> if nobody else is handling that backport.
> 
> Are you going to take a stab at the vCPU flags fix?

Yup, that's on my list. The backport will be easy down to 6.0, but way
more creative before that, as we don't have a proper flag management
infrastructure in older kernels.

Cheers,

	M.

-- 
Without deviation from the norm, progress is not possible.