* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-08-30 0:56 ` Jerome Glisse
0 siblings, 0 replies; 36+ messages in thread
From: Jerome Glisse @ 2017-08-30 0:56 UTC (permalink / raw)
To: Linus Torvalds
Cc: Bernhard Held, Adam Borowski, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Tue, Aug 29, 2017 at 05:11:24PM -0700, Linus Torvalds wrote:
> On Tue, Aug 29, 2017 at 4:54 PM, Jerome Glisse <jglisse@redhat.com> wrote:
> >
> > Note this is barely tested. I intend to do more testing of next few days
> > but i do not have access to all hardware that make use of the mmu_notifier
> > API.
>
> Thanks for doing this.
>
> > First 2 patches convert existing call of mmu_notifier_invalidate_page()
> > to mmu_notifier_invalidate_range() and bracket those call with call to
> > mmu_notifier_invalidate_range_start()/end().
>
> Ok, those two patches are a bit more complex than I was hoping for,
> but not *too* bad.
>
> And the final end result certainly looks nice:
>
> > 16 files changed, 74 insertions(+), 214 deletions(-)
>
> Yeah, removing all those invalidate_page() notifiers certainly makes
> for a nice patch.
>
> And I actually think you missed some more lines that can now be
> removed: kvm_arch_mmu_notifier_invalidate_page() should no longer be
> needed either, so you can remove all of those too (most of them are
> empty inline functions, but x86 has one that actually does something.
>
> So there's an added 30 or so dead lines that should be removed in the
> kvm patch, I think.
Yes i missed that. I will wait for people to test and for result of my
own test before reposting if need be, otherwise i will post as separate
patch.
>
> But from a _very_ quick read-through this looks fine. But it obviously
> needs testing.
>
> People - *especially* the people who saw issues under KVM - can you
> try out Jerome's patch-series? I aded some people to the cc, the full
> series is on lkml. Jerome - do you have a git branch for people to
> test that they could easily pull and try out?
https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
git://people.freedesktop.org/~glisse/linux
(Sorry if that tree is bit big it has a lot of dead thing i need
to push a clean and slim one)
Jerome
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-08-30 0:56 ` Jerome Glisse
0 siblings, 0 replies; 36+ messages in thread
From: Jerome Glisse @ 2017-08-30 0:56 UTC (permalink / raw)
To: Linus Torvalds
Cc: Bernhard Held, Adam Borowski, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Tue, Aug 29, 2017 at 05:11:24PM -0700, Linus Torvalds wrote:
> On Tue, Aug 29, 2017 at 4:54 PM, Jérôme Glisse <jglisse@redhat.com> wrote:
> >
> > Note this is barely tested. I intend to do more testing of next few days
> > but i do not have access to all hardware that make use of the mmu_notifier
> > API.
>
> Thanks for doing this.
>
> > First 2 patches convert existing call of mmu_notifier_invalidate_page()
> > to mmu_notifier_invalidate_range() and bracket those call with call to
> > mmu_notifier_invalidate_range_start()/end().
>
> Ok, those two patches are a bit more complex than I was hoping for,
> but not *too* bad.
>
> And the final end result certainly looks nice:
>
> > 16 files changed, 74 insertions(+), 214 deletions(-)
>
> Yeah, removing all those invalidate_page() notifiers certainly makes
> for a nice patch.
>
> And I actually think you missed some more lines that can now be
> removed: kvm_arch_mmu_notifier_invalidate_page() should no longer be
> needed either, so you can remove all of those too (most of them are
> empty inline functions, but x86 has one that actually does something.
>
> So there's an added 30 or so dead lines that should be removed in the
> kvm patch, I think.
Yes i missed that. I will wait for people to test and for result of my
own test before reposting if need be, otherwise i will post as separate
patch.
>
> But from a _very_ quick read-through this looks fine. But it obviously
> needs testing.
>
> People - *especially* the people who saw issues under KVM - can you
> try out Jérôme's patch-series? I aded some people to the cc, the full
> series is on lkml. Jérôme - do you have a git branch for people to
> test that they could easily pull and try out?
https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
git://people.freedesktop.org/~glisse/linux
(Sorry if that tree is bit big it has a lot of dead thing i need
to push a clean and slim one)
Jérôme
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
2017-08-30 0:56 ` Jerome Glisse
(?)
(?)
@ 2017-08-30 8:40 ` Mike Galbraith
-1 siblings, 0 replies; 36+ messages in thread
From: Mike Galbraith @ 2017-08-30 8:40 UTC (permalink / raw)
To: Jerome Glisse, Linus Torvalds
Cc: Bernhard Held, KVM list, Radim Krčmář,
Sudeep Dutt, DRI, linux-mm, Andrea Arcangeli, Dimitri Sivanich,
linux-rdma, amd-gfx, xen-devel, Adam Borowski, Joerg Roedel,
Jack Steiner, Dan Williams, Linux Kernel Mailing List,
Ashutosh Dixit, open list:AMD IOMMU (AMD-VI),
Paolo Bonzini, Andrew Morton, ppc-dev
On Tue, 2017-08-29 at 20:56 -0400, Jerome Glisse wrote:
> On Tue, Aug 29, 2017 at 05:11:24PM -0700, Linus Torvalds wrote:
>
> > People - *especially* the people who saw issues under KVM - can you
> > try out Jérôme's patch-series? I aded some people to the cc, the full
> > series is on lkml. Jérôme - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Looks good here.
I reproduced fairly quickly with RT host and 1 RT guest by just having
the guest do a parallel kbuild over NFS (the guest had to be restored
afterward, was corrupted). I'm currently flogging 2 guests as well as
the host, whimper free. I'll let the lot broil for while longer, but
at this point, smoke/flame appearance seems comfortingly unlikely.
-Mike
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
2017-08-30 0:56 ` Jerome Glisse
(?)
(?)
@ 2017-08-30 8:40 ` Mike Galbraith
-1 siblings, 0 replies; 36+ messages in thread
From: Mike Galbraith @ 2017-08-30 8:40 UTC (permalink / raw)
To: Jerome Glisse, Linus Torvalds
Cc: Bernhard Held, Adam Borowski, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel
On Tue, 2017-08-29 at 20:56 -0400, Jerome Glisse wrote:
> On Tue, Aug 29, 2017 at 05:11:24PM -0700, Linus Torvalds wrote:
>
> > People - *especially* the people who saw issues under KVM - can you
> > try out Jérôme's patch-series? I aded some people to the cc, the full
> > series is on lkml. Jérôme - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Looks good here.
I reproduced fairly quickly with RT host and 1 RT guest by just having
the guest do a parallel kbuild over NFS (the guest had to be restored
afterward, was corrupted). I'm currently flogging 2 guests as well as
the host, whimper free. I'll let the lot broil for while longer, but
at this point, smoke/flame appearance seems comfortingly unlikely.
-Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-08-30 8:40 ` Mike Galbraith
0 siblings, 0 replies; 36+ messages in thread
From: Mike Galbraith @ 2017-08-30 8:40 UTC (permalink / raw)
To: Jerome Glisse, Linus Torvalds
Cc: Bernhard Held, Adam Borowski, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Tue, 2017-08-29 at 20:56 -0400, Jerome Glisse wrote:
> On Tue, Aug 29, 2017 at 05:11:24PM -0700, Linus Torvalds wrote:
>=20
> > People - *especially* the people who saw issues under KVM - can you
> > try out J=C3=A9r=C3=B4me's patch-series? I aded some people to the cc, =
the full
> > series is on lkml. J=C3=A9r=C3=B4me - do you have a git branch for peop=
le to
> > test that they could easily pull and try out?
>=20
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Looks good here.
I reproduced fairly quickly with RT host and 1 RT guest by just having
the guest do a parallel kbuild over NFS (the guest had to be restored
afterward, was corrupted). =C2=A0I'm currently flogging 2 guests as well as
the host, whimper free. =C2=A0I'll let the lot broil for while longer, but
at this point, smoke/flame appearance seems comfortingly unlikely.
-Mike
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-08-30 8:40 ` Mike Galbraith
0 siblings, 0 replies; 36+ messages in thread
From: Mike Galbraith @ 2017-08-30 8:40 UTC (permalink / raw)
To: Jerome Glisse, Linus Torvalds
Cc: Bernhard Held, Adam Borowski, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Tue, 2017-08-29 at 20:56 -0400, Jerome Glisse wrote:
> On Tue, Aug 29, 2017 at 05:11:24PM -0700, Linus Torvalds wrote:
>
> > People - *especially* the people who saw issues under KVM - can you
> > try out Jérôme's patch-series? I aded some people to the cc, the full
> > series is on lkml. Jérôme - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Looks good here.
I reproduced fairly quickly with RT host and 1 RT guest by just having
the guest do a parallel kbuild over NFS (the guest had to be restored
afterward, was corrupted). I'm currently flogging 2 guests as well as
the host, whimper free. I'll let the lot broil for while longer, but
at this point, smoke/flame appearance seems comfortingly unlikely.
-Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-08-30 8:40 ` Mike Galbraith
0 siblings, 0 replies; 36+ messages in thread
From: Mike Galbraith @ 2017-08-30 8:40 UTC (permalink / raw)
To: Jerome Glisse, Linus Torvalds
Cc: Bernhard Held, Adam Borowski, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Tue, 2017-08-29 at 20:56 -0400, Jerome Glisse wrote:
> On Tue, Aug 29, 2017 at 05:11:24PM -0700, Linus Torvalds wrote:
>
> > People - *especially* the people who saw issues under KVM - can you
> > try out Jérôme's patch-series? I aded some people to the cc, the full
> > series is on lkml. Jérôme - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Looks good here.
I reproduced fairly quickly with RT host and 1 RT guest by just having
the guest do a parallel kbuild over NFS (the guest had to be restored
afterward, was corrupted). I'm currently flogging 2 guests as well as
the host, whimper free. I'll let the lot broil for while longer, but
at this point, smoke/flame appearance seems comfortingly unlikely.
-Mike
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
2017-08-30 0:56 ` Jerome Glisse
` (3 preceding siblings ...)
(?)
@ 2017-08-30 14:57 ` Adam Borowski
-1 siblings, 0 replies; 36+ messages in thread
From: Adam Borowski @ 2017-08-30 14:57 UTC (permalink / raw)
To: Jerome Glisse
Cc: Bernhard Held, KVM list, Radim Krčmář,
Sudeep Dutt, DRI, linux-mm, Andrea Arcangeli, Dimitri Sivanich,
linux-rdma, amd-gfx, xen-devel, Joerg Roedel, Jack Steiner,
Dan Williams, Linus Torvalds, Linux Kernel Mailing List,
Ashutosh Dixit, open list:AMD IOMMU (AMD-VI),
Paolo Bonzini, Andrew Morton, ppc-dev
On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> I will wait for people to test and for result of my own test before
> reposting if need be, otherwise i will post as separate patch.
>
> > But from a _very_ quick read-through this looks fine. But it obviously
> > needs testing.
> >
> > People - *especially* the people who saw issues under KVM - can you
> > try out Jérôme's patch-series? I aded some people to the cc, the full
> > series is on lkml. Jérôme - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Tested your branch as of 10f07641, on a long list of guest VMs.
No earth-shattering kaboom.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄⠀⠀⠀⠀
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
2017-08-30 0:56 ` Jerome Glisse
(?)
@ 2017-08-30 14:57 ` Adam Borowski
-1 siblings, 0 replies; 36+ messages in thread
From: Adam Borowski @ 2017-08-30 14:57 UTC (permalink / raw)
To: Jerome Glisse
Cc: Linus Torvalds, Bernhard Held, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI)
On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> I will wait for people to test and for result of my own test before
> reposting if need be, otherwise i will post as separate patch.
>
> > But from a _very_ quick read-through this looks fine. But it obviously
> > needs testing.
> >
> > People - *especially* the people who saw issues under KVM - can you
> > try out Jérôme's patch-series? I aded some people to the cc, the full
> > series is on lkml. Jérôme - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Tested your branch as of 10f07641, on a long list of guest VMs.
No earth-shattering kaboom.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄⠀⠀⠀⠀
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-08-30 14:57 ` Adam Borowski
0 siblings, 0 replies; 36+ messages in thread
From: Adam Borowski @ 2017-08-30 14:57 UTC (permalink / raw)
To: Jerome Glisse
Cc: Linus Torvalds, Bernhard Held, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> I will wait for people to test and for result of my own test before
> reposting if need be, otherwise i will post as separate patch.
>
> > But from a _very_ quick read-through this looks fine. But it obviously
> > needs testing.
> >
> > People - *especially* the people who saw issues under KVM - can you
> > try out JA(C)rA'me's patch-series? I aded some people to the cc, the full
> > series is on lkml. JA(C)rA'me - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Tested your branch as of 10f07641, on a long list of guest VMs.
No earth-shattering kaboom.
Meow!
--
ac?aGBP'a 3/4 a >>ac?aGBP|a ?
aGBP 3/4 a ?ac?a ?a ?aGBP?a!? Vat kind uf sufficiently advanced technology iz dis!?
ac?a!?a ?a .a ?a ?a ? -- Genghis Ht'rok'din
a ?a 3aGBP?a ?a ?a ?a ?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-08-30 14:57 ` Adam Borowski
0 siblings, 0 replies; 36+ messages in thread
From: Adam Borowski @ 2017-08-30 14:57 UTC (permalink / raw)
To: Jerome Glisse
Cc: Linus Torvalds, Bernhard Held, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> I will wait for people to test and for result of my own test before
> reposting if need be, otherwise i will post as separate patch.
>
> > But from a _very_ quick read-through this looks fine. But it obviously
> > needs testing.
> >
> > People - *especially* the people who saw issues under KVM - can you
> > try out Jérôme's patch-series? I aded some people to the cc, the full
> > series is on lkml. Jérôme - do you have a git branch for people to
> > test that they could easily pull and try out?
>
> https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> git://people.freedesktop.org/~glisse/linux
Tested your branch as of 10f07641, on a long list of guest VMs.
No earth-shattering kaboom.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄⠀⠀⠀⠀
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
2017-08-30 14:57 ` Adam Borowski
(?)
(?)
@ 2017-09-01 14:47 ` Jeff Cook
-1 siblings, 0 replies; 36+ messages in thread
From: Jeff Cook @ 2017-09-01 14:47 UTC (permalink / raw)
To: Adam Borowski, Jerome Glisse
Cc: Bernhard Held, KVM list, Radim Krčmář,
Sudeep Dutt, DRI, linux-mm, Andrea Arcangeli, Dimitri Sivanich,
linux-rdma, amd-gfx, xen-devel, Joerg Roedel, Jack Steiner,
Dan Williams, Linus Torvalds, Linux Kernel Mailing List,
Ashutosh Dixit, open list:AMD IOMMU (AMD-VI),
Paolo Bonzini, Andrew Morton, ppc-dev
On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote:
> On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> > I will wait for people to test and for result of my own test before
> > reposting if need be, otherwise i will post as separate patch.
> >
> > > But from a _very_ quick read-through this looks fine. But it obviously
> > > needs testing.
> > >
> > > People - *especially* the people who saw issues under KVM - can you
> > > try out Jérôme's patch-series? I aded some people to the cc, the full
> > > series is on lkml. Jérôme - do you have a git branch for people to
> > > test that they could easily pull and try out?
> >
> > https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> > git://people.freedesktop.org/~glisse/linux
>
> Tested your branch as of 10f07641, on a long list of guest VMs.
> No earth-shattering kaboom.
I've been using the mmu_notifier branch @ a3d944233bcf8c for the last 36
hours or so, also without incident.
Unlike most other reporters, I experienced a similar splat on 4.12:
Aug 03 15:02:47 kvm_master kernel: ------------[ cut here ]------------
Aug 03 15:02:47 kvm_master kernel: WARNING: CPU: 13 PID: 1653 at
arch/x86/kvm/mmu.c:682 mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: Modules linked in: vhost_net vhost
tap xt_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4
xt_tcpudp tun ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter msr nls_iso8859_1 nls_cp437 intel_rapl ipt_
MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel input_leds pcbc aesni_intel led_class
aes_x86_6
4 mxm_wmi crypto_simd glue_helper uvcvideo cryptd videobuf2_vmalloc
videobuf2_memops igb videobuf2_v4l2 videobuf2_core snd_usb_audio
videodev media joydev ptp evdev mousedev intel_cstate pps_core mac_hid
intel_rapl_perf snd_hda_intel snd_virtuoso snd_usbmidi_lib snd_hda_codec
snd_oxygen_lib snd_hda_core
Aug 03 15:02:47 kvm_master kernel: snd_mpu401_uart snd_rawmidi
snd_hwdep snd_seq_device snd_pcm snd_timer snd soundcore i2c_algo_bit
pcspkr i2c_i801 lpc_ich ioatdma shpchp dca wmi acpi_power_meter tpm_tis
tpm_tis_core tpm button bridge stp llc sch_fq_codel virtio_pci
virtio_blk virtio_balloon virtio_net virtio_ring virtio kvm_intel kvm sg
ip_tables x_tables hid_logitech_hidpp hid_logitech_dj hid_generic
hid_microsoft usbhid hid sr_mod cdrom sd_mod xhci_pci ahci libahci
xhci_hcd libata usbcore scsi_mod usb_common zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm vfio_pci irqbypass
vfio_virqfd vfio_iommu_type1 vfio vfat fat ext4 crc16 jbd2 fscrypto
mbcache dm_thin_pool dm_cache dm_persistent_data dm_bio_prison dm_bufio
dm_raid raid456 libcrc32c
Aug 03 15:02:47 kvm_master kernel: crc32c_generic crc32c_intel
async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq
dm_mod dax raid1 md_mod
Aug 03 15:02:47 kvm_master kernel: CPU: 13 PID: 1653 Comm: kworker/13:2
Tainted: P B D W O 4.12.3-1-ARCH #1
Aug 03 15:02:47 kvm_master kernel: Hardware name: Supermicro
SYS-7038A-I/X10DAI, BIOS 2.0a 11/09/2016
Aug 03 15:02:47 kvm_master kernel: Workqueue: events mmput_async_fn
Aug 03 15:02:47 kvm_master kernel: task: ffff9fa89751b900 task.stack:
ffffc179880d8000
Aug 03 15:02:47 kvm_master kernel: RIP:
0010:mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: RSP: 0018:ffffc179880dbc20 EFLAGS:
00010246
Aug 03 15:02:47 kvm_master kernel: RAX: 0000000000000000 RBX:
00000009c07cce77 RCX: dead0000000000ff
Aug 03 15:02:47 kvm_master kernel: RDX: 0000000000000000 RSI:
ffff9fa82d6d6f08 RDI: fffff6e76701f300
Aug 03 15:02:47 kvm_master kernel: RBP: ffffc179880dbc38 R08:
0000000000100000 R09: 000000000000000d
Aug 03 15:02:47 kvm_master kernel: R10: ffff9fa0a56b0008 R11:
ffff9fa0a56b0000 R12: 00000000009c07cc
Aug 03 15:02:47 kvm_master kernel: R13: ffff9fa88b990000 R14:
ffff9f9e19dbb1b8 R15: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: FS: 0000000000000000(0000)
GS:ffff9fac5f340000(0000) knlGS:0000000000000000
Aug 03 15:02:47 kvm_master kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Aug 03 15:02:47 kvm_master kernel: CR2: ffffd1b542d71000 CR3:
0000000570a09000 CR4: 00000000003426e0
Aug 03 15:02:47 kvm_master kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Aug 03 15:02:47 kvm_master kernel: Call Trace:
Aug 03 15:02:47 kvm_master kernel: drop_spte+0x1a/0xb0 [kvm]
Aug 03 15:02:47 kvm_master kernel: mmu_page_zap_pte+0x9c/0xe0 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_prepare_zap_page+0x65/0x310
[kvm]
Aug 03 15:02:47 kvm_master kernel:
kvm_mmu_invalidate_zap_all_pages+0x10d/0x160 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_arch_flush_shadow_all+0xe/0x10
[kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_notifier_release+0x2c/0x40
[kvm]
Aug 03 15:02:47 kvm_master kernel: __mmu_notifier_release+0x44/0xc0
Aug 03 15:02:47 kvm_master kernel: exit_mmap+0x142/0x150
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? exit_aio+0xc6/0x100
Aug 03 15:02:47 kvm_master kernel: mmput_async_fn+0x4c/0x130
Aug 03 15:02:47 kvm_master kernel: process_one_work+0x1de/0x430
Aug 03 15:02:47 kvm_master kernel: worker_thread+0x47/0x3f0
Aug 03 15:02:47 kvm_master kernel: kthread+0x125/0x140
Aug 03 15:02:47 kvm_master kernel: ? process_one_work+0x430/0x430
Aug 03 15:02:47 kvm_master kernel: ? kthread_create_on_node+0x70/0x70
Aug 03 15:02:47 kvm_master kernel: ret_from_fork+0x25/0x30
Aug 03 15:02:47 kvm_master kernel: Code: ec 75 04 00 48 b8 00 00 00 00
00 00 00 40 48 21 da 48 39 c2 0f 95 c0 eb b2 48 d1 eb 83 e3 01 eb c0 4c
89 e7 e8 f7 3d fe ff eb a4 <0f> ff eb 8a 90 0f 1f 44 00 00 55 48 89 e5
53 89 d3 e8 ff 4a fe
Aug 03 15:02:47 kvm_master kernel: ---[ end trace 8710f4d700a7d36e ]---
This would typically take 36-48 hours to surface, so we're good so far,
but not completely out of the woods yet. I'm optimistic that since this
patchset changes the mmu_notifier behavior to something safer in
general, this issue will also be resolved by it.
Jeff
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
> ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
> ⠈⠳⣄⠀⠀⠀⠀
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
2017-08-30 14:57 ` Adam Borowski
(?)
(?)
@ 2017-09-01 14:47 ` Jeff Cook
-1 siblings, 0 replies; 36+ messages in thread
From: Jeff Cook @ 2017-09-01 14:47 UTC (permalink / raw)
To: Adam Borowski, Jerome Glisse
Cc: Linus Torvalds, Bernhard Held, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel
On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote:
> On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> > I will wait for people to test and for result of my own test before
> > reposting if need be, otherwise i will post as separate patch.
> >
> > > But from a _very_ quick read-through this looks fine. But it obviously
> > > needs testing.
> > >
> > > People - *especially* the people who saw issues under KVM - can you
> > > try out Jérôme's patch-series? I aded some people to the cc, the full
> > > series is on lkml. Jérôme - do you have a git branch for people to
> > > test that they could easily pull and try out?
> >
> > https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> > git://people.freedesktop.org/~glisse/linux
>
> Tested your branch as of 10f07641, on a long list of guest VMs.
> No earth-shattering kaboom.
I've been using the mmu_notifier branch @ a3d944233bcf8c for the last 36
hours or so, also without incident.
Unlike most other reporters, I experienced a similar splat on 4.12:
Aug 03 15:02:47 kvm_master kernel: ------------[ cut here ]------------
Aug 03 15:02:47 kvm_master kernel: WARNING: CPU: 13 PID: 1653 at
arch/x86/kvm/mmu.c:682 mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: Modules linked in: vhost_net vhost
tap xt_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4
xt_tcpudp tun ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter msr nls_iso8859_1 nls_cp437 intel_rapl ipt_
MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel input_leds pcbc aesni_intel led_class
aes_x86_6
4 mxm_wmi crypto_simd glue_helper uvcvideo cryptd videobuf2_vmalloc
videobuf2_memops igb videobuf2_v4l2 videobuf2_core snd_usb_audio
videodev media joydev ptp evdev mousedev intel_cstate pps_core mac_hid
intel_rapl_perf snd_hda_intel snd_virtuoso snd_usbmidi_lib snd_hda_codec
snd_oxygen_lib snd_hda_core
Aug 03 15:02:47 kvm_master kernel: snd_mpu401_uart snd_rawmidi
snd_hwdep snd_seq_device snd_pcm snd_timer snd soundcore i2c_algo_bit
pcspkr i2c_i801 lpc_ich ioatdma shpchp dca wmi acpi_power_meter tpm_tis
tpm_tis_core tpm button bridge stp llc sch_fq_codel virtio_pci
virtio_blk virtio_balloon virtio_net virtio_ring virtio kvm_intel kvm sg
ip_tables x_tables hid_logitech_hidpp hid_logitech_dj hid_generic
hid_microsoft usbhid hid sr_mod cdrom sd_mod xhci_pci ahci libahci
xhci_hcd libata usbcore scsi_mod usb_common zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm vfio_pci irqbypass
vfio_virqfd vfio_iommu_type1 vfio vfat fat ext4 crc16 jbd2 fscrypto
mbcache dm_thin_pool dm_cache dm_persistent_data dm_bio_prison dm_bufio
dm_raid raid456 libcrc32c
Aug 03 15:02:47 kvm_master kernel: crc32c_generic crc32c_intel
async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq
dm_mod dax raid1 md_mod
Aug 03 15:02:47 kvm_master kernel: CPU: 13 PID: 1653 Comm: kworker/13:2
Tainted: P B D W O 4.12.3-1-ARCH #1
Aug 03 15:02:47 kvm_master kernel: Hardware name: Supermicro
SYS-7038A-I/X10DAI, BIOS 2.0a 11/09/2016
Aug 03 15:02:47 kvm_master kernel: Workqueue: events mmput_async_fn
Aug 03 15:02:47 kvm_master kernel: task: ffff9fa89751b900 task.stack:
ffffc179880d8000
Aug 03 15:02:47 kvm_master kernel: RIP:
0010:mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: RSP: 0018:ffffc179880dbc20 EFLAGS:
00010246
Aug 03 15:02:47 kvm_master kernel: RAX: 0000000000000000 RBX:
00000009c07cce77 RCX: dead0000000000ff
Aug 03 15:02:47 kvm_master kernel: RDX: 0000000000000000 RSI:
ffff9fa82d6d6f08 RDI: fffff6e76701f300
Aug 03 15:02:47 kvm_master kernel: RBP: ffffc179880dbc38 R08:
0000000000100000 R09: 000000000000000d
Aug 03 15:02:47 kvm_master kernel: R10: ffff9fa0a56b0008 R11:
ffff9fa0a56b0000 R12: 00000000009c07cc
Aug 03 15:02:47 kvm_master kernel: R13: ffff9fa88b990000 R14:
ffff9f9e19dbb1b8 R15: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: FS: 0000000000000000(0000)
GS:ffff9fac5f340000(0000) knlGS:0000000000000000
Aug 03 15:02:47 kvm_master kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Aug 03 15:02:47 kvm_master kernel: CR2: ffffd1b542d71000 CR3:
0000000570a09000 CR4: 00000000003426e0
Aug 03 15:02:47 kvm_master kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Aug 03 15:02:47 kvm_master kernel: Call Trace:
Aug 03 15:02:47 kvm_master kernel: drop_spte+0x1a/0xb0 [kvm]
Aug 03 15:02:47 kvm_master kernel: mmu_page_zap_pte+0x9c/0xe0 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_prepare_zap_page+0x65/0x310
[kvm]
Aug 03 15:02:47 kvm_master kernel:
kvm_mmu_invalidate_zap_all_pages+0x10d/0x160 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_arch_flush_shadow_all+0xe/0x10
[kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_notifier_release+0x2c/0x40
[kvm]
Aug 03 15:02:47 kvm_master kernel: __mmu_notifier_release+0x44/0xc0
Aug 03 15:02:47 kvm_master kernel: exit_mmap+0x142/0x150
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? exit_aio+0xc6/0x100
Aug 03 15:02:47 kvm_master kernel: mmput_async_fn+0x4c/0x130
Aug 03 15:02:47 kvm_master kernel: process_one_work+0x1de/0x430
Aug 03 15:02:47 kvm_master kernel: worker_thread+0x47/0x3f0
Aug 03 15:02:47 kvm_master kernel: kthread+0x125/0x140
Aug 03 15:02:47 kvm_master kernel: ? process_one_work+0x430/0x430
Aug 03 15:02:47 kvm_master kernel: ? kthread_create_on_node+0x70/0x70
Aug 03 15:02:47 kvm_master kernel: ret_from_fork+0x25/0x30
Aug 03 15:02:47 kvm_master kernel: Code: ec 75 04 00 48 b8 00 00 00 00
00 00 00 40 48 21 da 48 39 c2 0f 95 c0 eb b2 48 d1 eb 83 e3 01 eb c0 4c
89 e7 e8 f7 3d fe ff eb a4 <0f> ff eb 8a 90 0f 1f 44 00 00 55 48 89 e5
53 89 d3 e8 ff 4a fe
Aug 03 15:02:47 kvm_master kernel: ---[ end trace 8710f4d700a7d36e ]---
This would typically take 36-48 hours to surface, so we're good so far,
but not completely out of the woods yet. I'm optimistic that since this
patchset changes the mmu_notifier behavior to something safer in
general, this issue will also be resolved by it.
Jeff
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
> ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
> ⠈⠳⣄⠀⠀⠀⠀
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-09-01 14:47 ` Jeff Cook
0 siblings, 0 replies; 36+ messages in thread
From: Jeff Cook @ 2017-09-01 14:47 UTC (permalink / raw)
To: Adam Borowski, Jerome Glisse
Cc: Linus Torvalds, Bernhard Held, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote:
> On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> > I will wait for people to test and for result of my own test before
> > reposting if need be, otherwise i will post as separate patch.
> >
> > > But from a _very_ quick read-through this looks fine. But it obviously
> > > needs testing.
> > >=20
> > > People - *especially* the people who saw issues under KVM - can you
> > > try out J=C3=A9r=C3=B4me's patch-series? I aded some people to the cc=
, the full
> > > series is on lkml. J=C3=A9r=C3=B4me - do you have a git branch for pe=
ople to
> > > test that they could easily pull and try out?
> >=20
> > https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> > git://people.freedesktop.org/~glisse/linux
>=20
> Tested your branch as of 10f07641, on a long list of guest VMs.
> No earth-shattering kaboom.
I've been using the mmu_notifier branch @ a3d944233bcf8c for the last 36
hours or so, also without incident.
Unlike most other reporters, I experienced a similar splat on 4.12:
Aug 03 15:02:47 kvm_master kernel: ------------[ cut here ]------------
Aug 03 15:02:47 kvm_master kernel: WARNING: CPU: 13 PID: 1653 at
arch/x86/kvm/mmu.c:682 mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: Modules linked in: vhost_net vhost
tap xt_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4
xt_tcpudp tun ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter msr nls_iso8859_1 nls_cp437 intel_rapl ipt_
MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel input_leds pcbc aesni_intel led_class
aes_x86_6
4 mxm_wmi crypto_simd glue_helper uvcvideo cryptd videobuf2_vmalloc
videobuf2_memops igb videobuf2_v4l2 videobuf2_core snd_usb_audio
videodev media joydev ptp evdev mousedev intel_cstate pps_core mac_hid
intel_rapl_perf snd_hda_intel snd_virtuoso snd_usbmidi_lib snd_hda_codec
snd_oxygen_lib snd_hda_core=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: snd_mpu401_uart snd_rawmidi
snd_hwdep snd_seq_device snd_pcm snd_timer snd soundcore i2c_algo_bit
pcspkr i2c_i801 lpc_ich ioatdma shpchp dca wmi acpi_power_meter tpm_tis
tpm_tis_core tpm button bridge stp llc sch_fq_codel virtio_pci
virtio_blk virtio_balloon virtio_net virtio_ring virtio kvm_intel kvm sg
ip_tables x_tables hid_logitech_hidpp hid_logitech_dj hid_generic
hid_microsoft usbhid hid sr_mod cdrom sd_mod xhci_pci ahci libahci
xhci_hcd libata usbcore scsi_mod usb_common zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm vfio_pci irqbypass
vfio_virqfd vfio_iommu_type1 vfio vfat fat ext4 crc16 jbd2 fscrypto
mbcache dm_thin_pool dm_cache dm_persistent_data dm_bio_prison dm_bufio
dm_raid raid456 libcrc32c=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: crc32c_generic crc32c_intel
async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq
dm_mod dax raid1 md_mod=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: CPU: 13 PID: 1653 Comm: kworker/13:2
Tainted: P B D W O 4.12.3-1-ARCH #1=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: Hardware name: Supermicro
SYS-7038A-I/X10DAI, BIOS 2.0a 11/09/2016=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: Workqueue: events mmput_async_fn=20=20=
=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: task: ffff9fa89751b900 task.stack:
ffffc179880d8000=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20
Aug 03 15:02:47 kvm_master kernel: RIP:
0010:mmu_spte_clear_track_bits+0xfb/0x100 [kvm]=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: RSP: 0018:ffffc179880dbc20 EFLAGS:
00010246=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: RAX: 0000000000000000 RBX:
00000009c07cce77 RCX: dead0000000000ff=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: RDX: 0000000000000000 RSI:
ffff9fa82d6d6f08 RDI: fffff6e76701f300=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: RBP: ffffc179880dbc38 R08:
0000000000100000 R09: 000000000000000d=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: R10: ffff9fa0a56b0008 R11:
ffff9fa0a56b0000 R12: 00000000009c07cc=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: R13: ffff9fa88b990000 R14:
ffff9f9e19dbb1b8 R15: 0000000000000000=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: FS: 0000000000000000(0000)
GS:ffff9fac5f340000(0000) knlGS:0000000000000000=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20
Aug 03 15:02:47 kvm_master kernel: CR2: ffffd1b542d71000 CR3:
0000000570a09000 CR4: 00000000003426e0=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: Call Trace:=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: drop_spte+0x1a/0xb0 [kvm]=20=20=20=20
Aug 03 15:02:47 kvm_master kernel: mmu_page_zap_pte+0x9c/0xe0 [kvm]=20=20=
=20=20=20
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_prepare_zap_page+0x65/0x310
[kvm]
Aug 03 15:02:47 kvm_master kernel:=20
kvm_mmu_invalidate_zap_all_pages+0x10d/0x160 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_arch_flush_shadow_all+0xe/0x10
[kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_notifier_release+0x2c/0x40
[kvm]
Aug 03 15:02:47 kvm_master kernel: __mmu_notifier_release+0x44/0xc0
Aug 03 15:02:47 kvm_master kernel: exit_mmap+0x142/0x150
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? exit_aio+0xc6/0x100
Aug 03 15:02:47 kvm_master kernel: mmput_async_fn+0x4c/0x130
Aug 03 15:02:47 kvm_master kernel: process_one_work+0x1de/0x430
Aug 03 15:02:47 kvm_master kernel: worker_thread+0x47/0x3f0
Aug 03 15:02:47 kvm_master kernel: kthread+0x125/0x140
Aug 03 15:02:47 kvm_master kernel: ? process_one_work+0x430/0x430
Aug 03 15:02:47 kvm_master kernel: ? kthread_create_on_node+0x70/0x70
Aug 03 15:02:47 kvm_master kernel: ret_from_fork+0x25/0x30
Aug 03 15:02:47 kvm_master kernel: Code: ec 75 04 00 48 b8 00 00 00 00
00 00 00 40 48 21 da 48 39 c2 0f 95 c0 eb b2 48 d1 eb 83 e3 01 eb c0 4c
89 e7 e8 f7 3d fe ff eb a4 <0f> ff eb 8a 90 0f 1f 44 00 00 55 48 89 e5
53 89 d3 e8 ff 4a fe=20
Aug 03 15:02:47 kvm_master kernel: ---[ end trace 8710f4d700a7d36e ]---
This would typically take 36-48 hours to surface, so we're good so far,
but not completely out of the woods yet. I'm optimistic that since this
patchset changes the mmu_notifier behavior to something safer in
general, this issue will also be resolved by it.
Jeff
>=20
>=20
> Meow!
> --=20
> =E2=A2=80=E2=A3=B4=E2=A0=BE=E2=A0=BB=E2=A2=B6=E2=A3=A6=E2=A0=80=20
> =E2=A3=BE=E2=A0=81=E2=A2=B0=E2=A0=92=E2=A0=80=E2=A3=BF=E2=A1=81 Vat kind =
uf sufficiently advanced technology iz dis!?
> =E2=A2=BF=E2=A1=84=E2=A0=98=E2=A0=B7=E2=A0=9A=E2=A0=8B=E2=A0=80 =
-- Genghis Ht'rok'din
> =E2=A0=88=E2=A0=B3=E2=A3=84=E2=A0=80=E2=A0=80=E2=A0=80=E2=A0=80=20
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-09-01 14:47 ` Jeff Cook
0 siblings, 0 replies; 36+ messages in thread
From: Jeff Cook @ 2017-09-01 14:47 UTC (permalink / raw)
To: Adam Borowski, Jerome Glisse
Cc: Linus Torvalds, Bernhard Held, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote:
> On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> > I will wait for people to test and for result of my own test before
> > reposting if need be, otherwise i will post as separate patch.
> >
> > > But from a _very_ quick read-through this looks fine. But it obviously
> > > needs testing.
> > >
> > > People - *especially* the people who saw issues under KVM - can you
> > > try out Jérôme's patch-series? I aded some people to the cc, the full
> > > series is on lkml. Jérôme - do you have a git branch for people to
> > > test that they could easily pull and try out?
> >
> > https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> > git://people.freedesktop.org/~glisse/linux
>
> Tested your branch as of 10f07641, on a long list of guest VMs.
> No earth-shattering kaboom.
I've been using the mmu_notifier branch @ a3d944233bcf8c for the last 36
hours or so, also without incident.
Unlike most other reporters, I experienced a similar splat on 4.12:
Aug 03 15:02:47 kvm_master kernel: ------------[ cut here ]------------
Aug 03 15:02:47 kvm_master kernel: WARNING: CPU: 13 PID: 1653 at
arch/x86/kvm/mmu.c:682 mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: Modules linked in: vhost_net vhost
tap xt_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4
xt_tcpudp tun ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter msr nls_iso8859_1 nls_cp437 intel_rapl ipt_
MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel input_leds pcbc aesni_intel led_class
aes_x86_6
4 mxm_wmi crypto_simd glue_helper uvcvideo cryptd videobuf2_vmalloc
videobuf2_memops igb videobuf2_v4l2 videobuf2_core snd_usb_audio
videodev media joydev ptp evdev mousedev intel_cstate pps_core mac_hid
intel_rapl_perf snd_hda_intel snd_virtuoso snd_usbmidi_lib snd_hda_codec
snd_oxygen_lib snd_hda_core
Aug 03 15:02:47 kvm_master kernel: snd_mpu401_uart snd_rawmidi
snd_hwdep snd_seq_device snd_pcm snd_timer snd soundcore i2c_algo_bit
pcspkr i2c_i801 lpc_ich ioatdma shpchp dca wmi acpi_power_meter tpm_tis
tpm_tis_core tpm button bridge stp llc sch_fq_codel virtio_pci
virtio_blk virtio_balloon virtio_net virtio_ring virtio kvm_intel kvm sg
ip_tables x_tables hid_logitech_hidpp hid_logitech_dj hid_generic
hid_microsoft usbhid hid sr_mod cdrom sd_mod xhci_pci ahci libahci
xhci_hcd libata usbcore scsi_mod usb_common zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm vfio_pci irqbypass
vfio_virqfd vfio_iommu_type1 vfio vfat fat ext4 crc16 jbd2 fscrypto
mbcache dm_thin_pool dm_cache dm_persistent_data dm_bio_prison dm_bufio
dm_raid raid456 libcrc32c
Aug 03 15:02:47 kvm_master kernel: crc32c_generic crc32c_intel
async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq
dm_mod dax raid1 md_mod
Aug 03 15:02:47 kvm_master kernel: CPU: 13 PID: 1653 Comm: kworker/13:2
Tainted: P B D W O 4.12.3-1-ARCH #1
Aug 03 15:02:47 kvm_master kernel: Hardware name: Supermicro
SYS-7038A-I/X10DAI, BIOS 2.0a 11/09/2016
Aug 03 15:02:47 kvm_master kernel: Workqueue: events mmput_async_fn
Aug 03 15:02:47 kvm_master kernel: task: ffff9fa89751b900 task.stack:
ffffc179880d8000
Aug 03 15:02:47 kvm_master kernel: RIP:
0010:mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: RSP: 0018:ffffc179880dbc20 EFLAGS:
00010246
Aug 03 15:02:47 kvm_master kernel: RAX: 0000000000000000 RBX:
00000009c07cce77 RCX: dead0000000000ff
Aug 03 15:02:47 kvm_master kernel: RDX: 0000000000000000 RSI:
ffff9fa82d6d6f08 RDI: fffff6e76701f300
Aug 03 15:02:47 kvm_master kernel: RBP: ffffc179880dbc38 R08:
0000000000100000 R09: 000000000000000d
Aug 03 15:02:47 kvm_master kernel: R10: ffff9fa0a56b0008 R11:
ffff9fa0a56b0000 R12: 00000000009c07cc
Aug 03 15:02:47 kvm_master kernel: R13: ffff9fa88b990000 R14:
ffff9f9e19dbb1b8 R15: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: FS: 0000000000000000(0000)
GS:ffff9fac5f340000(0000) knlGS:0000000000000000
Aug 03 15:02:47 kvm_master kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Aug 03 15:02:47 kvm_master kernel: CR2: ffffd1b542d71000 CR3:
0000000570a09000 CR4: 00000000003426e0
Aug 03 15:02:47 kvm_master kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Aug 03 15:02:47 kvm_master kernel: Call Trace:
Aug 03 15:02:47 kvm_master kernel: drop_spte+0x1a/0xb0 [kvm]
Aug 03 15:02:47 kvm_master kernel: mmu_page_zap_pte+0x9c/0xe0 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_prepare_zap_page+0x65/0x310
[kvm]
Aug 03 15:02:47 kvm_master kernel:
kvm_mmu_invalidate_zap_all_pages+0x10d/0x160 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_arch_flush_shadow_all+0xe/0x10
[kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_notifier_release+0x2c/0x40
[kvm]
Aug 03 15:02:47 kvm_master kernel: __mmu_notifier_release+0x44/0xc0
Aug 03 15:02:47 kvm_master kernel: exit_mmap+0x142/0x150
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? exit_aio+0xc6/0x100
Aug 03 15:02:47 kvm_master kernel: mmput_async_fn+0x4c/0x130
Aug 03 15:02:47 kvm_master kernel: process_one_work+0x1de/0x430
Aug 03 15:02:47 kvm_master kernel: worker_thread+0x47/0x3f0
Aug 03 15:02:47 kvm_master kernel: kthread+0x125/0x140
Aug 03 15:02:47 kvm_master kernel: ? process_one_work+0x430/0x430
Aug 03 15:02:47 kvm_master kernel: ? kthread_create_on_node+0x70/0x70
Aug 03 15:02:47 kvm_master kernel: ret_from_fork+0x25/0x30
Aug 03 15:02:47 kvm_master kernel: Code: ec 75 04 00 48 b8 00 00 00 00
00 00 00 40 48 21 da 48 39 c2 0f 95 c0 eb b2 48 d1 eb 83 e3 01 eb c0 4c
89 e7 e8 f7 3d fe ff eb a4 <0f> ff eb 8a 90 0f 1f 44 00 00 55 48 89 e5
53 89 d3 e8 ff 4a fe
Aug 03 15:02:47 kvm_master kernel: ---[ end trace 8710f4d700a7d36e ]---
This would typically take 36-48 hours to surface, so we're good so far,
but not completely out of the woods yet. I'm optimistic that since this
patchset changes the mmu_notifier behavior to something safer in
general, this issue will also be resolved by it.
Jeff
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
> ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
> ⠈⠳⣄⠀⠀⠀⠀
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-09-01 14:47 ` Jeff Cook
0 siblings, 0 replies; 36+ messages in thread
From: Jeff Cook @ 2017-09-01 14:47 UTC (permalink / raw)
To: Adam Borowski, Jerome Glisse
Cc: Linus Torvalds, Bernhard Held, Linux Kernel Mailing List,
linux-mm, Kirill A . Shutemov, Andrew Morton, Andrea Arcangeli,
Joerg Roedel, Dan Williams, Sudeep Dutt, Ashutosh Dixit,
Dimitri Sivanich, Jack Steiner, Paolo Bonzini,
Radim Krčmář,
ppc-dev, DRI, amd-gfx, linux-rdma, open list:AMD IOMMU (AMD-VI),
xen-devel, KVM list
On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote:
> On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> > I will wait for people to test and for result of my own test before
> > reposting if need be, otherwise i will post as separate patch.
> >
> > > But from a _very_ quick read-through this looks fine. But it obviously
> > > needs testing.
> > >
> > > People - *especially* the people who saw issues under KVM - can you
> > > try out Jérôme's patch-series? I aded some people to the cc, the full
> > > series is on lkml. Jérôme - do you have a git branch for people to
> > > test that they could easily pull and try out?
> >
> > https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> > git://people.freedesktop.org/~glisse/linux
>
> Tested your branch as of 10f07641, on a long list of guest VMs.
> No earth-shattering kaboom.
I've been using the mmu_notifier branch @ a3d944233bcf8c for the last 36
hours or so, also without incident.
Unlike most other reporters, I experienced a similar splat on 4.12:
Aug 03 15:02:47 kvm_master kernel: ------------[ cut here ]------------
Aug 03 15:02:47 kvm_master kernel: WARNING: CPU: 13 PID: 1653 at
arch/x86/kvm/mmu.c:682 mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: Modules linked in: vhost_net vhost
tap xt_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4
xt_tcpudp tun ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter msr nls_iso8859_1 nls_cp437 intel_rapl ipt_
MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel input_leds pcbc aesni_intel led_class
aes_x86_6
4 mxm_wmi crypto_simd glue_helper uvcvideo cryptd videobuf2_vmalloc
videobuf2_memops igb videobuf2_v4l2 videobuf2_core snd_usb_audio
videodev media joydev ptp evdev mousedev intel_cstate pps_core mac_hid
intel_rapl_perf snd_hda_intel snd_virtuoso snd_usbmidi_lib snd_hda_codec
snd_oxygen_lib snd_hda_core
Aug 03 15:02:47 kvm_master kernel: snd_mpu401_uart snd_rawmidi
snd_hwdep snd_seq_device snd_pcm snd_timer snd soundcore i2c_algo_bit
pcspkr i2c_i801 lpc_ich ioatdma shpchp dca wmi acpi_power_meter tpm_tis
tpm_tis_core tpm button bridge stp llc sch_fq_codel virtio_pci
virtio_blk virtio_balloon virtio_net virtio_ring virtio kvm_intel kvm sg
ip_tables x_tables hid_logitech_hidpp hid_logitech_dj hid_generic
hid_microsoft usbhid hid sr_mod cdrom sd_mod xhci_pci ahci libahci
xhci_hcd libata usbcore scsi_mod usb_common zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm vfio_pci irqbypass
vfio_virqfd vfio_iommu_type1 vfio vfat fat ext4 crc16 jbd2 fscrypto
mbcache dm_thin_pool dm_cache dm_persistent_data dm_bio_prison dm_bufio
dm_raid raid456 libcrc32c
Aug 03 15:02:47 kvm_master kernel: crc32c_generic crc32c_intel
async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq
dm_mod dax raid1 md_mod
Aug 03 15:02:47 kvm_master kernel: CPU: 13 PID: 1653 Comm: kworker/13:2
Tainted: P B D W O 4.12.3-1-ARCH #1
Aug 03 15:02:47 kvm_master kernel: Hardware name: Supermicro
SYS-7038A-I/X10DAI, BIOS 2.0a 11/09/2016
Aug 03 15:02:47 kvm_master kernel: Workqueue: events mmput_async_fn
Aug 03 15:02:47 kvm_master kernel: task: ffff9fa89751b900 task.stack:
ffffc179880d8000
Aug 03 15:02:47 kvm_master kernel: RIP:
0010:mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: RSP: 0018:ffffc179880dbc20 EFLAGS:
00010246
Aug 03 15:02:47 kvm_master kernel: RAX: 0000000000000000 RBX:
00000009c07cce77 RCX: dead0000000000ff
Aug 03 15:02:47 kvm_master kernel: RDX: 0000000000000000 RSI:
ffff9fa82d6d6f08 RDI: fffff6e76701f300
Aug 03 15:02:47 kvm_master kernel: RBP: ffffc179880dbc38 R08:
0000000000100000 R09: 000000000000000d
Aug 03 15:02:47 kvm_master kernel: R10: ffff9fa0a56b0008 R11:
ffff9fa0a56b0000 R12: 00000000009c07cc
Aug 03 15:02:47 kvm_master kernel: R13: ffff9fa88b990000 R14:
ffff9f9e19dbb1b8 R15: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: FS: 0000000000000000(0000)
GS:ffff9fac5f340000(0000) knlGS:0000000000000000
Aug 03 15:02:47 kvm_master kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Aug 03 15:02:47 kvm_master kernel: CR2: ffffd1b542d71000 CR3:
0000000570a09000 CR4: 00000000003426e0
Aug 03 15:02:47 kvm_master kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Aug 03 15:02:47 kvm_master kernel: Call Trace:
Aug 03 15:02:47 kvm_master kernel: drop_spte+0x1a/0xb0 [kvm]
Aug 03 15:02:47 kvm_master kernel: mmu_page_zap_pte+0x9c/0xe0 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_prepare_zap_page+0x65/0x310
[kvm]
Aug 03 15:02:47 kvm_master kernel:
kvm_mmu_invalidate_zap_all_pages+0x10d/0x160 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_arch_flush_shadow_all+0xe/0x10
[kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_notifier_release+0x2c/0x40
[kvm]
Aug 03 15:02:47 kvm_master kernel: __mmu_notifier_release+0x44/0xc0
Aug 03 15:02:47 kvm_master kernel: exit_mmap+0x142/0x150
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? exit_aio+0xc6/0x100
Aug 03 15:02:47 kvm_master kernel: mmput_async_fn+0x4c/0x130
Aug 03 15:02:47 kvm_master kernel: process_one_work+0x1de/0x430
Aug 03 15:02:47 kvm_master kernel: worker_thread+0x47/0x3f0
Aug 03 15:02:47 kvm_master kernel: kthread+0x125/0x140
Aug 03 15:02:47 kvm_master kernel: ? process_one_work+0x430/0x430
Aug 03 15:02:47 kvm_master kernel: ? kthread_create_on_node+0x70/0x70
Aug 03 15:02:47 kvm_master kernel: ret_from_fork+0x25/0x30
Aug 03 15:02:47 kvm_master kernel: Code: ec 75 04 00 48 b8 00 00 00 00
00 00 00 40 48 21 da 48 39 c2 0f 95 c0 eb b2 48 d1 eb 83 e3 01 eb c0 4c
89 e7 e8 f7 3d fe ff eb a4 <0f> ff eb 8a 90 0f 1f 44 00 00 55 48 89 e5
53 89 d3 e8 ff 4a fe
Aug 03 15:02:47 kvm_master kernel: ---[ end trace 8710f4d700a7d36e ]---
This would typically take 36-48 hours to surface, so we're good so far,
but not completely out of the woods yet. I'm optimistic that since this
patchset changes the mmu_notifier behavior to something safer in
general, this issue will also be resolved by it.
Jeff
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
> ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
> ⠈⠳⣄⠀⠀⠀⠀
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
2017-09-01 14:47 ` Jeff Cook
@ 2017-09-01 14:50 ` taskboxtester
-1 siblings, 0 replies; 36+ messages in thread
From: taskboxtester @ 2017-09-01 14:50 UTC (permalink / raw)
To: Jeff Cook
Cc: open list:AMD IOMMU (AMD-VI),
Paolo Bonzini, Dan Williams, linux-rdma, Jack Steiner,
Dimitri Sivanich, Bernhard Held, Andrew Morton,
Radim Krčmář,
amd-gfx, DRI, xen-devel, Joerg Roedel, Jerome Glisse, ppc-dev,
Linus Torvalds, Kirill A . Shutemov, Andrea Arcangeli,
Sudeep Dutt, KVM list, Adam Borowski
[-- Attachment #1: Type: text/plain, Size: 7403 bytes --]
taskboxtester@gmail.com liked your message with Boxer for Android.
On Sep 1, 2017 10:48 AM, Jeff Cook <jeff@jeffcook.io> wrote:
On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote:
> On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> > I will wait for people to test and for result of my own test before
> > reposting if need be, otherwise i will post as separate patch.
> >
> > > But from a _very_ quick read-through this looks fine. But it obviously
> > > needs testing.
> > >
> > > People - *especially* the people who saw issues under KVM - can you
> > > try out Jérôme's patch-series? I aded some people to the cc, the full
> > > series is on lkml. Jérôme - do you have a git branch for people to
> > > test that they could easily pull and try out?
> >
> > https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> > git://people.freedesktop.org/~glisse/linux
>
> Tested your branch as of 10f07641, on a long list of guest VMs.
> No earth-shattering kaboom.
I've been using the mmu_notifier branch @ a3d944233bcf8c for the last 36
hours or so, also without incident.
Unlike most other reporters, I experienced a similar splat on 4.12:
Aug 03 15:02:47 kvm_master kernel: ------------[ cut here ]------------
Aug 03 15:02:47 kvm_master kernel: WARNING: CPU: 13 PID: 1653 at
arch/x86/kvm/mmu.c:682 mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: Modules linked in: vhost_net vhost
tap xt_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4
xt_tcpudp tun ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter msr nls_iso8859_1 nls_cp437 intel_rapl ipt_
MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel input_leds pcbc aesni_intel led_class
aes_x86_6
4 mxm_wmi crypto_simd glue_helper uvcvideo cryptd videobuf2_vmalloc
videobuf2_memops igb videobuf2_v4l2 videobuf2_core snd_usb_audio
videodev media joydev ptp evdev mousedev intel_cstate pps_core mac_hid
intel_rapl_perf snd_hda_intel snd_virtuoso snd_usbmidi_lib snd_hda_codec
snd_oxygen_lib snd_hda_core
Aug 03 15:02:47 kvm_master kernel: snd_mpu401_uart snd_rawmidi
snd_hwdep snd_seq_device snd_pcm snd_timer snd soundcore i2c_algo_bit
pcspkr i2c_i801 lpc_ich ioatdma shpchp dca wmi acpi_power_meter tpm_tis
tpm_tis_core tpm button bridge stp llc sch_fq_codel virtio_pci
virtio_blk virtio_balloon virtio_net virtio_ring virtio kvm_intel kvm sg
ip_tables x_tables hid_logitech_hidpp hid_logitech_dj hid_generic
hid_microsoft usbhid hid sr_mod cdrom sd_mod xhci_pci ahci libahci
xhci_hcd libata usbcore scsi_mod usb_common zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm vfio_pci irqbypass
vfio_virqfd vfio_iommu_type1 vfio vfat fat ext4 crc16 jbd2 fscrypto
mbcache dm_thin_pool dm_cache dm_persistent_data dm_bio_prison dm_bufio
dm_raid raid456 libcrc32c
Aug 03 15:02:47 kvm_master kernel: crc32c_generic crc32c_intel
async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq
dm_mod dax raid1 md_mod
Aug 03 15:02:47 kvm_master kernel: CPU: 13 PID: 1653 Comm: kworker/13:2
Tainted: P B D W O 4.12.3-1-ARCH #1
Aug 03 15:02:47 kvm_master kernel: Hardware name: Supermicro
SYS-7038A-I/X10DAI, BIOS 2.0a 11/09/2016
Aug 03 15:02:47 kvm_master kernel: Workqueue: events mmput_async_fn
Aug 03 15:02:47 kvm_master kernel: task: ffff9fa89751b900 task.stack:
ffffc179880d8000
Aug 03 15:02:47 kvm_master kernel: RIP:
0010:mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: RSP: 0018:ffffc179880dbc20 EFLAGS:
00010246
Aug 03 15:02:47 kvm_master kernel: RAX: 0000000000000000 RBX:
00000009c07cce77 RCX: dead0000000000ff
Aug 03 15:02:47 kvm_master kernel: RDX: 0000000000000000 RSI:
ffff9fa82d6d6f08 RDI: fffff6e76701f300
Aug 03 15:02:47 kvm_master kernel: RBP: ffffc179880dbc38 R08:
0000000000100000 R09: 000000000000000d
Aug 03 15:02:47 kvm_master kernel: R10: ffff9fa0a56b0008 R11:
ffff9fa0a56b0000 R12: 00000000009c07cc
Aug 03 15:02:47 kvm_master kernel: R13: ffff9fa88b990000 R14:
ffff9f9e19dbb1b8 R15: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: FS: 0000000000000000(0000)
GS:ffff9fac5f340000(0000) knlGS:0000000000000000
Aug 03 15:02:47 kvm_master kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Aug 03 15:02:47 kvm_master kernel: CR2: ffffd1b542d71000 CR3:
0000000570a09000 CR4: 00000000003426e0
Aug 03 15:02:47 kvm_master kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Aug 03 15:02:47 kvm_master kernel: Call Trace:
Aug 03 15:02:47 kvm_master kernel: drop_spte+0x1a/0xb0 [kvm]
Aug 03 15:02:47 kvm_master kernel: mmu_page_zap_pte+0x9c/0xe0 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_prepare_zap_page+0x65/0x310
[kvm]
Aug 03 15:02:47 kvm_master kernel:
kvm_mmu_invalidate_zap_all_pages+0x10d/0x160 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_arch_flush_shadow_all+0xe/0x10
[kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_notifier_release+0x2c/0x40
[kvm]
Aug 03 15:02:47 kvm_master kernel: __mmu_notifier_release+0x44/0xc0
Aug 03 15:02:47 kvm_master kernel: exit_mmap+0x142/0x150
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? exit_aio+0xc6/0x100
Aug 03 15:02:47 kvm_master kernel: mmput_async_fn+0x4c/0x130
Aug 03 15:02:47 kvm_master kernel: process_one_work+0x1de/0x430
Aug 03 15:02:47 kvm_master kernel: worker_thread+0x47/0x3f0
Aug 03 15:02:47 kvm_master kernel: kthread+0x125/0x140
Aug 03 15:02:47 kvm_master kernel: ? process_one_work+0x430/0x430
Aug 03 15:02:47 kvm_master kernel: ? kthread_create_on_node+0x70/0x70
Aug 03 15:02:47 kvm_master kernel: ret_from_fork+0x25/0x30
Aug 03 15:02:47 kvm_master kernel: Code: ec 75 04 00 48 b8 00 00 00 00
00 00 00 40 48 21 da 48 39 c2 0f 95 c0 eb b2 48 d1 eb 83 e3 01 eb c0 4c
89 e7 e8 f7 3d fe ff eb a4 <0f> ff eb 8a 90 0f 1f 44 00 00 55 48 89 e5
53 89 d3 e8 ff 4a fe
Aug 03 15:02:47 kvm_master kernel: ---[ end trace 8710f4d700a7d36e ]---
This would typically take 36-48 hours to surface, so we're good so far,
but not completely out of the woods yet. I'm optimistic that since this
patchset changes the mmu_notifier behavior to something safer in
general, this issue will also be resolved by it.
Jeff
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
> ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
> ⠈⠳⣄⠀⠀⠀⠀
[-- Attachment #2: Type: text/html, Size: 12378 bytes --]
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH 00/13] mmu_notifier kill invalidate_page callback
@ 2017-09-01 14:50 ` taskboxtester
0 siblings, 0 replies; 36+ messages in thread
From: taskboxtester @ 2017-09-01 14:50 UTC (permalink / raw)
To: Jeff Cook
Cc: open list:AMD IOMMU (AMD-VI),
Paolo Bonzini, Dan Williams, linux-rdma, Jack Steiner,
Dimitri Sivanich, Bernhard Held, Andrew Morton,
Radim Krčmář,
amd-gfx, DRI, xen-devel, Joerg Roedel, Jerome Glisse, ppc-dev,
Linus Torvalds, Kirill A . Shutemov, Andrea Arcangeli,
Sudeep Dutt, KVM list, Adam Borowski, Linux Kernel Mailing List,
Ashutosh Dixit, linux-mm
[-- Attachment #1: Type: text/plain, Size: 7403 bytes --]
taskboxtester@gmail.com liked your message with Boxer for Android.
On Sep 1, 2017 10:48 AM, Jeff Cook <jeff@jeffcook.io> wrote:
On Wed, Aug 30, 2017, at 10:57 AM, Adam Borowski wrote:
> On Tue, Aug 29, 2017 at 08:56:15PM -0400, Jerome Glisse wrote:
> > I will wait for people to test and for result of my own test before
> > reposting if need be, otherwise i will post as separate patch.
> >
> > > But from a _very_ quick read-through this looks fine. But it obviously
> > > needs testing.
> > >
> > > People - *especially* the people who saw issues under KVM - can you
> > > try out Jérôme's patch-series? I aded some people to the cc, the full
> > > series is on lkml. Jérôme - do you have a git branch for people to
> > > test that they could easily pull and try out?
> >
> > https://cgit.freedesktop.org/~glisse/linux mmu-notifier branch
> > git://people.freedesktop.org/~glisse/linux
>
> Tested your branch as of 10f07641, on a long list of guest VMs.
> No earth-shattering kaboom.
I've been using the mmu_notifier branch @ a3d944233bcf8c for the last 36
hours or so, also without incident.
Unlike most other reporters, I experienced a similar splat on 4.12:
Aug 03 15:02:47 kvm_master kernel: ------------[ cut here ]------------
Aug 03 15:02:47 kvm_master kernel: WARNING: CPU: 13 PID: 1653 at
arch/x86/kvm/mmu.c:682 mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: Modules linked in: vhost_net vhost
tap xt_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4
xt_tcpudp tun ebtable_filter ebtables ip6table_filter ip6_tables
iptable_filter msr nls_iso8859_1 nls_cp437 intel_rapl ipt_
MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack sb_edac
x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel input_leds pcbc aesni_intel led_class
aes_x86_6
4 mxm_wmi crypto_simd glue_helper uvcvideo cryptd videobuf2_vmalloc
videobuf2_memops igb videobuf2_v4l2 videobuf2_core snd_usb_audio
videodev media joydev ptp evdev mousedev intel_cstate pps_core mac_hid
intel_rapl_perf snd_hda_intel snd_virtuoso snd_usbmidi_lib snd_hda_codec
snd_oxygen_lib snd_hda_core
Aug 03 15:02:47 kvm_master kernel: snd_mpu401_uart snd_rawmidi
snd_hwdep snd_seq_device snd_pcm snd_timer snd soundcore i2c_algo_bit
pcspkr i2c_i801 lpc_ich ioatdma shpchp dca wmi acpi_power_meter tpm_tis
tpm_tis_core tpm button bridge stp llc sch_fq_codel virtio_pci
virtio_blk virtio_balloon virtio_net virtio_ring virtio kvm_intel kvm sg
ip_tables x_tables hid_logitech_hidpp hid_logitech_dj hid_generic
hid_microsoft usbhid hid sr_mod cdrom sd_mod xhci_pci ahci libahci
xhci_hcd libata usbcore scsi_mod usb_common zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) drm_kms_helper
syscopyarea sysfillrect sysimgblt fb_sys_fops drm vfio_pci irqbypass
vfio_virqfd vfio_iommu_type1 vfio vfat fat ext4 crc16 jbd2 fscrypto
mbcache dm_thin_pool dm_cache dm_persistent_data dm_bio_prison dm_bufio
dm_raid raid456 libcrc32c
Aug 03 15:02:47 kvm_master kernel: crc32c_generic crc32c_intel
async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq
dm_mod dax raid1 md_mod
Aug 03 15:02:47 kvm_master kernel: CPU: 13 PID: 1653 Comm: kworker/13:2
Tainted: P B D W O 4.12.3-1-ARCH #1
Aug 03 15:02:47 kvm_master kernel: Hardware name: Supermicro
SYS-7038A-I/X10DAI, BIOS 2.0a 11/09/2016
Aug 03 15:02:47 kvm_master kernel: Workqueue: events mmput_async_fn
Aug 03 15:02:47 kvm_master kernel: task: ffff9fa89751b900 task.stack:
ffffc179880d8000
Aug 03 15:02:47 kvm_master kernel: RIP:
0010:mmu_spte_clear_track_bits+0xfb/0x100 [kvm]
Aug 03 15:02:47 kvm_master kernel: RSP: 0018:ffffc179880dbc20 EFLAGS:
00010246
Aug 03 15:02:47 kvm_master kernel: RAX: 0000000000000000 RBX:
00000009c07cce77 RCX: dead0000000000ff
Aug 03 15:02:47 kvm_master kernel: RDX: 0000000000000000 RSI:
ffff9fa82d6d6f08 RDI: fffff6e76701f300
Aug 03 15:02:47 kvm_master kernel: RBP: ffffc179880dbc38 R08:
0000000000100000 R09: 000000000000000d
Aug 03 15:02:47 kvm_master kernel: R10: ffff9fa0a56b0008 R11:
ffff9fa0a56b0000 R12: 00000000009c07cc
Aug 03 15:02:47 kvm_master kernel: R13: ffff9fa88b990000 R14:
ffff9f9e19dbb1b8 R15: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: FS: 0000000000000000(0000)
GS:ffff9fac5f340000(0000) knlGS:0000000000000000
Aug 03 15:02:47 kvm_master kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Aug 03 15:02:47 kvm_master kernel: CR2: ffffd1b542d71000 CR3:
0000000570a09000 CR4: 00000000003426e0
Aug 03 15:02:47 kvm_master kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Aug 03 15:02:47 kvm_master kernel: DR3: 0000000000000000 DR6:
00000000fffe0ff0 DR7: 0000000000000400
Aug 03 15:02:47 kvm_master kernel: Call Trace:
Aug 03 15:02:47 kvm_master kernel: drop_spte+0x1a/0xb0 [kvm]
Aug 03 15:02:47 kvm_master kernel: mmu_page_zap_pte+0x9c/0xe0 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_prepare_zap_page+0x65/0x310
[kvm]
Aug 03 15:02:47 kvm_master kernel:
kvm_mmu_invalidate_zap_all_pages+0x10d/0x160 [kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_arch_flush_shadow_all+0xe/0x10
[kvm]
Aug 03 15:02:47 kvm_master kernel: kvm_mmu_notifier_release+0x2c/0x40
[kvm]
Aug 03 15:02:47 kvm_master kernel: __mmu_notifier_release+0x44/0xc0
Aug 03 15:02:47 kvm_master kernel: exit_mmap+0x142/0x150
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? kfree+0x175/0x190
Aug 03 15:02:47 kvm_master kernel: ? exit_aio+0xc6/0x100
Aug 03 15:02:47 kvm_master kernel: mmput_async_fn+0x4c/0x130
Aug 03 15:02:47 kvm_master kernel: process_one_work+0x1de/0x430
Aug 03 15:02:47 kvm_master kernel: worker_thread+0x47/0x3f0
Aug 03 15:02:47 kvm_master kernel: kthread+0x125/0x140
Aug 03 15:02:47 kvm_master kernel: ? process_one_work+0x430/0x430
Aug 03 15:02:47 kvm_master kernel: ? kthread_create_on_node+0x70/0x70
Aug 03 15:02:47 kvm_master kernel: ret_from_fork+0x25/0x30
Aug 03 15:02:47 kvm_master kernel: Code: ec 75 04 00 48 b8 00 00 00 00
00 00 00 40 48 21 da 48 39 c2 0f 95 c0 eb b2 48 d1 eb 83 e3 01 eb c0 4c
89 e7 e8 f7 3d fe ff eb a4 <0f> ff eb 8a 90 0f 1f 44 00 00 55 48 89 e5
53 89 d3 e8 ff 4a fe
Aug 03 15:02:47 kvm_master kernel: ---[ end trace 8710f4d700a7d36e ]---
This would typically take 36-48 hours to surface, so we're good so far,
but not completely out of the woods yet. I'm optimistic that since this
patchset changes the mmu_notifier behavior to something safer in
general, this issue will also be resolved by it.
Jeff
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
> ⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
> ⠈⠳⣄⠀⠀⠀⠀
[-- Attachment #2: Type: text/html, Size: 12378 bytes --]
^ permalink raw reply [flat|nested] 36+ messages in thread