Hi Paolo, On Fri, 05 Mar 2021 17:27:36 +0000, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > On 05/03/21 17:49, Marc Zyngier wrote: > > Hi Paolo, > > > > Here's the first batch of fixes for 5.12. We have a handful of low > > level world-switch regressions, a page table walker fix, more PMU > > tidying up, and a workaround for systems with creative firmware. > > > > Note that this is based on -rc1 despite the breakage, as I didn't feel > > like holding these patches until -rc2. > > > > Please pull, > > > > M. > > > > The following changes since commit fe07bfda2fb9cdef8a4d4008a409bb02f35f1bd8: > > > > Linux 5.12-rc1 (2021-02-28 16:05:19 -0800) > > > > are available in the Git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-5.12-1 > > > > for you to fetch changes up to e85583b3f1fe62c9b371a3100c1c91af94005ca9: > > > > KVM: arm64: Fix range alignment when walking page tables (2021-03-04 09:54:12 +0000) > > Hi Marc, > > due to a severe data corruption bug in 5.12-rc1, Linus suggested not > including 5.12-rc1 in trees to avoid it eating our filesystems > unwittingly during future bisections. > > Would it be a problem for you to rebase on top of your merge window > pull request? If there are conflicts, another possibility is for you > to just send me the patch series. I will handle all the topic branch > juggling. > > This will mean rewriting kvmarm.git's history, but it does seem to be > the lesser (or the most future-proof) evil. The problem is that this is not only kvmarm, but also the Android tree, which directly pulls from the kvmarm stable branches. I guess we'll have to live with it. I'll reply to this email with the patch series. Thanks, M. -- Without deviation from the norm, progress is not possible.
