Re: [PATCH v2 00/17] KVM: Dirty ring interface

From: Peter Xu
Date: Fri Dec 20 2019 - 16:38:11 EST

Next message: Mathieu Desnoyers: "[RFC PATCH glibc 10/13] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux (v5)"
Previous message: syzbot: "KASAN: use-after-free Read in io_wq_flush"
In reply to: Peter Xu: "[PATCH v2 03/17] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR]"
Next in thread: Sean Christopherson: "Re: [PATCH v2 00/17] KVM: Dirty ring interface"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

If you see three identical half-posted series which only contains
patches 00-09... I am very sorry for ruining your inbox... I think my
mail server is not happy to continue sending the rest of the patches,
and I'll get this during sending the patch 10:

4.3.0 Temporary System Problem. Try again later (10). d25sm3385231qtq.11 - gsmtp

So far I don't see what's wrong with patch 10, either.

I'll try to fix it up before I send 4th time (or anyone knows please
hint me)... Please ignore the previous three in-complete versions.

--
Peter Xu

Next message: Mathieu Desnoyers: "[RFC PATCH glibc 10/13] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux (v5)"
Previous message: syzbot: "KASAN: use-after-free Read in io_wq_flush"
In reply to: Peter Xu: "[PATCH v2 03/17] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR]"
Next in thread: Sean Christopherson: "Re: [PATCH v2 00/17] KVM: Dirty ring interface"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]