2017-11-30 12:20+0100, Paolo Bonzini: > On 30/11/2017 10:33, Fabian Grünbichler wrote: > > > > It was reverted in 785373b4c38719f4af6775845df6be1dfaea120f after which > > the symptoms disappeared until this series was merged, which contains > > > > 369ea8242c0fb5239b4ddf0dc568f694bd244de4 mm/rmap: update to new mmu_notifier semantic v2 > > > > We haven't bisected the individual commits of the series yet, but the > > commit immediately preceding its merge exhibits no problems, while > > everything after does. It is not known whether the bug is actually in > > the series itself, or whether increasing the likelihood of triggering it > > is just a side-effect. There is a similar report[2] concerning an > > upgrade from 4.12.12 to 4.12.13, which does not contain this series in > > any form AFAICT but might be worth another look as well. > > I know of one issue in this series (invalidate_page was removed from KVM > without reimplementing it as invalidate_range). I'll try to prioritize > the fix, but I don't think I can do it before Monday. The series also dropped the reloading of the APIC access page and we never had it in invalidate_range_start ... I'll look into it today.
