* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
[not found] ` <6c5567f4-192d-aefd-90e4-89f53479c24e@redhat.com>
@ 2017-02-24 2:23 ` Herongguang (Stephen)
2017-02-24 9:35 ` Herongguang (Stephen)
2017-02-24 15:10 ` Chris Friesen
0 siblings, 2 replies; 12+ messages in thread
From: Herongguang (Stephen) @ 2017-02-24 2:23 UTC (permalink / raw)
To: Paolo Bonzini, Chris Friesen, Han, Huaitong, hangaohuai, stable
Cc: kvm, fangying1, xudong.hao, qemu-devel, wangxinxin.wang,
kai.huang, rkrcmar, guangrong.xiao, linux-kernel
On 2017/2/22 22:43, Paolo Bonzini wrote:
>
>
> On 22/02/2017 14:31, Chris Friesen wrote:
>>>>
>>>
>>> Can you reproduce it with kernel 4.8+? I'm suspecting commmit
>>> 4e59516a12a6 ("kvm: vmx: ensure VMCS is current while enabling PML",
>>> 2016-07-14) to be the fix.
>>
>> I can't easily try with a newer kernel, the software package we're using
>> has kernel patches that would have to be ported.
>>
>> I'm at a conference, don't really have time to set up a pair of test
>> machines from scratch with a custom kernel.
>
> Hopefully Gaohuai and Rongguang can help with this too.
>
> Paolo
>
> .
>
Yes, we are looking into and testing this.
I think this can result in any memory corruption, if VM1 writes its
PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
is not registered yet), then VM1 is destroyed (hence its PML buffer
is freed back to kernel), after that, VM2 starts migration, so CPU
logs VM2’s dirty GFNS into a freed memory, results in any memory corruption.
As its severity, this commit (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
is eligible to back port to kernel stable.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-24 2:23 ` [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration Herongguang (Stephen)
@ 2017-02-24 9:35 ` Herongguang (Stephen)
2017-02-24 9:59 ` Greg KH
2017-02-24 15:10 ` Chris Friesen
1 sibling, 1 reply; 12+ messages in thread
From: Herongguang (Stephen) @ 2017-02-24 9:35 UTC (permalink / raw)
To: gregkh
Cc: Paolo Bonzini, Chris Friesen, Han, Huaitong, hangaohuai, stable,
kvm, fangying1, xudong.hao, qemu-devel, wangxinxin.wang,
kai.huang, rkrcmar, guangrong.xiao, linux-kernel
On 2017/2/24 10:23, Herongguang (Stephen) wrote:
>
>
> On 2017/2/22 22:43, Paolo Bonzini wrote:
>>
>>
>> On 22/02/2017 14:31, Chris Friesen wrote:
>>>>>
>>>>
>>>> Can you reproduce it with kernel 4.8+? I'm suspecting commmit
>>>> 4e59516a12a6 ("kvm: vmx: ensure VMCS is current while enabling PML",
>>>> 2016-07-14) to be the fix.
>>>
>>> I can't easily try with a newer kernel, the software package we're using
>>> has kernel patches that would have to be ported.
>>>
>>> I'm at a conference, don't really have time to set up a pair of test
>>> machines from scratch with a custom kernel.
>>
>> Hopefully Gaohuai and Rongguang can help with this too.
>>
>> Paolo
>>
>> .
>>
> Yes, we are looking into and testing this.
>
> I think this can result in any memory corruption, if VM1 writes its
> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
> is not registered yet), then VM1 is destroyed (hence its PML buffer
> is freed back to kernel), after that, VM2 starts migration, so CPU
> logs VM2’s dirty GFNS into a freed memory, results in any memory corruption.
>
> As its severity, this commit (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
> is eligible to back port to kernel stable.
Hi, Greg, can you cherry pick commit 4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec to 4.4-y?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-24 9:35 ` Herongguang (Stephen)
@ 2017-02-24 9:59 ` Greg KH
2017-02-24 10:00 ` Paolo Bonzini
0 siblings, 1 reply; 12+ messages in thread
From: Greg KH @ 2017-02-24 9:59 UTC (permalink / raw)
To: Herongguang (Stephen)
Cc: Paolo Bonzini, Chris Friesen, Han, Huaitong, hangaohuai, stable,
kvm, fangying1, xudong.hao, qemu-devel, wangxinxin.wang,
kai.huang, rkrcmar, guangrong.xiao, linux-kernel
On Fri, Feb 24, 2017 at 05:35:17PM +0800, Herongguang (Stephen) wrote:
>
>
> On 2017/2/24 10:23, Herongguang (Stephen) wrote:
> >
> >
> > On 2017/2/22 22:43, Paolo Bonzini wrote:
> > >
> > >
> > > On 22/02/2017 14:31, Chris Friesen wrote:
> > > > > >
> > > > >
> > > > > Can you reproduce it with kernel 4.8+? I'm suspecting commmit
> > > > > 4e59516a12a6 ("kvm: vmx: ensure VMCS is current while enabling PML",
> > > > > 2016-07-14) to be the fix.
> > > >
> > > > I can't easily try with a newer kernel, the software package we're using
> > > > has kernel patches that would have to be ported.
> > > >
> > > > I'm at a conference, don't really have time to set up a pair of test
> > > > machines from scratch with a custom kernel.
> > >
> > > Hopefully Gaohuai and Rongguang can help with this too.
> > >
> > > Paolo
> > >
> > > .
> > >
> > Yes, we are looking into and testing this.
> >
> > I think this can result in any memory corruption, if VM1 writes its
> > PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
> > is not registered yet), then VM1 is destroyed (hence its PML buffer
> > is freed back to kernel), after that, VM2 starts migration, so CPU
> > logs VM2’s dirty GFNS into a freed memory, results in any memory corruption.
> >
> > As its severity, this commit (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
> > is eligible to back port to kernel stable.
>
> Hi, Greg, can you cherry pick commit 4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec to 4.4-y?
If the KVM maintainers say it is ok to do so, yes, I will.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-24 9:59 ` Greg KH
@ 2017-02-24 10:00 ` Paolo Bonzini
2017-02-24 10:07 ` Greg KH
0 siblings, 1 reply; 12+ messages in thread
From: Paolo Bonzini @ 2017-02-24 10:00 UTC (permalink / raw)
To: Greg KH, Herongguang (Stephen)
Cc: Chris Friesen, Han, Huaitong, hangaohuai, stable, kvm, fangying1,
xudong.hao, qemu-devel, wangxinxin.wang, kai.huang, rkrcmar,
guangrong.xiao, linux-kernel
On 24/02/2017 10:59, Greg KH wrote:
> On Fri, Feb 24, 2017 at 05:35:17PM +0800, Herongguang (Stephen) wrote:
>>
>>
>> On 2017/2/24 10:23, Herongguang (Stephen) wrote:
>>>
>>>
>>> On 2017/2/22 22:43, Paolo Bonzini wrote:
>>>>
>>>>
>>>> On 22/02/2017 14:31, Chris Friesen wrote:
>>>>>>>
>>>>>>
>>>>>> Can you reproduce it with kernel 4.8+? I'm suspecting commmit
>>>>>> 4e59516a12a6 ("kvm: vmx: ensure VMCS is current while enabling PML",
>>>>>> 2016-07-14) to be the fix.
>>>>>
>>>>> I can't easily try with a newer kernel, the software package we're using
>>>>> has kernel patches that would have to be ported.
>>>>>
>>>>> I'm at a conference, don't really have time to set up a pair of test
>>>>> machines from scratch with a custom kernel.
>>>>
>>>> Hopefully Gaohuai and Rongguang can help with this too.
>>>>
>>>> Paolo
>>>>
>>>> .
>>>>
>>> Yes, we are looking into and testing this.
>>>
>>> I think this can result in any memory corruption, if VM1 writes its
>>> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
>>> is not registered yet), then VM1 is destroyed (hence its PML buffer
>>> is freed back to kernel), after that, VM2 starts migration, so CPU
>>> logs VM2’s dirty GFNS into a freed memory, results in any memory corruption.
>>>
>>> As its severity, this commit (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
>>> is eligible to back port to kernel stable.
>>
>> Hi, Greg, can you cherry pick commit 4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec to 4.4-y?
>
> If the KVM maintainers say it is ok to do so, yes, I will.
Yes, he beat me by minutes. :)
Paolo
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-24 10:00 ` Paolo Bonzini
@ 2017-02-24 10:07 ` Greg KH
0 siblings, 0 replies; 12+ messages in thread
From: Greg KH @ 2017-02-24 10:07 UTC (permalink / raw)
To: Paolo Bonzini
Cc: Herongguang (Stephen),
Chris Friesen, Han, Huaitong, hangaohuai, stable, kvm, fangying1,
xudong.hao, qemu-devel, wangxinxin.wang, kai.huang, rkrcmar,
guangrong.xiao, linux-kernel
On Fri, Feb 24, 2017 at 11:00:32AM +0100, Paolo Bonzini wrote:
>
>
> On 24/02/2017 10:59, Greg KH wrote:
> > On Fri, Feb 24, 2017 at 05:35:17PM +0800, Herongguang (Stephen) wrote:
> >>
> >>
> >> On 2017/2/24 10:23, Herongguang (Stephen) wrote:
> >>>
> >>>
> >>> On 2017/2/22 22:43, Paolo Bonzini wrote:
> >>>>
> >>>>
> >>>> On 22/02/2017 14:31, Chris Friesen wrote:
> >>>>>>>
> >>>>>>
> >>>>>> Can you reproduce it with kernel 4.8+? I'm suspecting commmit
> >>>>>> 4e59516a12a6 ("kvm: vmx: ensure VMCS is current while enabling PML",
> >>>>>> 2016-07-14) to be the fix.
> >>>>>
> >>>>> I can't easily try with a newer kernel, the software package we're using
> >>>>> has kernel patches that would have to be ported.
> >>>>>
> >>>>> I'm at a conference, don't really have time to set up a pair of test
> >>>>> machines from scratch with a custom kernel.
> >>>>
> >>>> Hopefully Gaohuai and Rongguang can help with this too.
> >>>>
> >>>> Paolo
> >>>>
> >>>> .
> >>>>
> >>> Yes, we are looking into and testing this.
> >>>
> >>> I think this can result in any memory corruption, if VM1 writes its
> >>> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
> >>> is not registered yet), then VM1 is destroyed (hence its PML buffer
> >>> is freed back to kernel), after that, VM2 starts migration, so CPU
> >>> logs VM2’s dirty GFNS into a freed memory, results in any memory corruption.
> >>>
> >>> As its severity, this commit (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
> >>> is eligible to back port to kernel stable.
> >>
> >> Hi, Greg, can you cherry pick commit 4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec to 4.4-y?
> >
> > If the KVM maintainers say it is ok to do so, yes, I will.
>
> Yes, he beat me by minutes. :)
Heh, ok, I'll go add it to the recently-announced 4.4.52-rc1 release.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-24 2:23 ` [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration Herongguang (Stephen)
2017-02-24 9:35 ` Herongguang (Stephen)
@ 2017-02-24 15:10 ` Chris Friesen
2017-02-24 15:14 ` Paolo Bonzini
1 sibling, 1 reply; 12+ messages in thread
From: Chris Friesen @ 2017-02-24 15:10 UTC (permalink / raw)
To: Herongguang (Stephen), Paolo Bonzini, Han, Huaitong, hangaohuai, stable
Cc: kvm, fangying1, xudong.hao, qemu-devel, wangxinxin.wang,
kai.huang, rkrcmar, guangrong.xiao, linux-kernel
On 02/23/2017 08:23 PM, Herongguang (Stephen) wrote:
> On 2017/2/22 22:43, Paolo Bonzini wrote:
>> Hopefully Gaohuai and Rongguang can help with this too.
>>
>> Paolo
>>
>> .
>>
> Yes, we are looking into and testing this.
>
> I think this can result in any memory corruption, if VM1 writes its
> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
> is not registered yet), then VM1 is destroyed (hence its PML buffer
> is freed back to kernel), after that, VM2 starts migration, so CPU
> logs VM2’s dirty GFNS into a freed memory, results in any memory corruption.
>
> As its severity, this commit
> (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
>
> is eligible to back port to kernel stable.
>
Are we expecting that fix to resolve the original issue, or is it a separate
issue that needs fixing in stable?
Chris
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-24 15:10 ` Chris Friesen
@ 2017-02-24 15:14 ` Paolo Bonzini
2017-02-25 1:44 ` Herongguang (Stephen)
0 siblings, 1 reply; 12+ messages in thread
From: Paolo Bonzini @ 2017-02-24 15:14 UTC (permalink / raw)
To: Chris Friesen, Herongguang (Stephen), Han, Huaitong, hangaohuai, stable
Cc: kvm, fangying1, xudong.hao, qemu-devel, wangxinxin.wang,
kai.huang, rkrcmar, guangrong.xiao, linux-kernel
On 24/02/2017 16:10, Chris Friesen wrote:
> On 02/23/2017 08:23 PM, Herongguang (Stephen) wrote:
>
>> On 2017/2/22 22:43, Paolo Bonzini wrote:
>
>>> Hopefully Gaohuai and Rongguang can help with this too.
>>>
>>> Paolo
>>
>> Yes, we are looking into and testing this.
>>
>> I think this can result in any memory corruption, if VM1 writes its
>> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
>> is not registered yet), then VM1 is destroyed (hence its PML buffer
>> is freed back to kernel), after that, VM2 starts migration, so CPU
>> logs VM2’s dirty GFNS into a freed memory, results in any memory
>> corruption.
>>
>> As its severity, this commit
>> (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
>>
>> is eligible to back port to kernel stable.
>
> Are we expecting that fix to resolve the original issue, or is it a
> separate issue that needs fixing in stable?
It should be the original issue.
Paolo
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-24 15:14 ` Paolo Bonzini
@ 2017-02-25 1:44 ` Herongguang (Stephen)
2017-02-27 7:38 ` Huang, Kai
0 siblings, 1 reply; 12+ messages in thread
From: Herongguang (Stephen) @ 2017-02-25 1:44 UTC (permalink / raw)
To: Paolo Bonzini, Chris Friesen, Han, Huaitong, hangaohuai, stable
Cc: kvm, fangying1, xudong.hao, qemu-devel, wangxinxin.wang,
kai.huang, rkrcmar, guangrong.xiao, linux-kernel
On 2017/2/24 23:14, Paolo Bonzini wrote:
>
>
> On 24/02/2017 16:10, Chris Friesen wrote:
>> On 02/23/2017 08:23 PM, Herongguang (Stephen) wrote:
>>
>>> On 2017/2/22 22:43, Paolo Bonzini wrote:
>>
>>>> Hopefully Gaohuai and Rongguang can help with this too.
>>>>
>>>> Paolo
>>>
>>> Yes, we are looking into and testing this.
>>>
>>> I think this can result in any memory corruption, if VM1 writes its
>>> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
>>> is not registered yet), then VM1 is destroyed (hence its PML buffer
>>> is freed back to kernel), after that, VM2 starts migration, so CPU
>>> logs VM2’s dirty GFNS into a freed memory, results in any memory
>>> corruption.
>>>
>>> As its severity, this commit
>>> (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
>>>
>>> is eligible to back port to kernel stable.
>>
>> Are we expecting that fix to resolve the original issue, or is it a
>> separate issue that needs fixing in stable?
>
> It should be the original issue.
>
> Paolo
>
> .
>
Yes, I agree, though we are still testing.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-25 1:44 ` Herongguang (Stephen)
@ 2017-02-27 7:38 ` Huang, Kai
2017-03-13 14:58 ` fangying
0 siblings, 1 reply; 12+ messages in thread
From: Huang, Kai @ 2017-02-27 7:38 UTC (permalink / raw)
To: Herongguang (Stephen),
Paolo Bonzini, Chris Friesen, Han, Huaitong, hangaohuai, stable
Cc: kvm, fangying1, xudong.hao, qemu-devel, wangxinxin.wang, rkrcmar,
guangrong.xiao, linux-kernel
On 2/25/2017 2:44 PM, Herongguang (Stephen) wrote:
>
>
> On 2017/2/24 23:14, Paolo Bonzini wrote:
>>
>>
>> On 24/02/2017 16:10, Chris Friesen wrote:
>>> On 02/23/2017 08:23 PM, Herongguang (Stephen) wrote:
>>>
>>>> On 2017/2/22 22:43, Paolo Bonzini wrote:
>>>
>>>>> Hopefully Gaohuai and Rongguang can help with this too.
>>>>>
>>>>> Paolo
>>>>
>>>> Yes, we are looking into and testing this.
>>>>
>>>> I think this can result in any memory corruption, if VM1 writes its
>>>> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
>>>> is not registered yet), then VM1 is destroyed (hence its PML buffer
>>>> is freed back to kernel), after that, VM2 starts migration, so CPU
>>>> logs VM2’s dirty GFNS into a freed memory, results in any memory
>>>> corruption.
>>>>
>>>> As its severity, this commit
>>>> (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
>>>>
>>>>
>>>> is eligible to back port to kernel stable.
>>>
>>> Are we expecting that fix to resolve the original issue, or is it a
>>> separate issue that needs fixing in stable?
>>
>> It should be the original issue.
>>
>> Paolo
>>
>> .
>>
> Yes, I agree, though we are still testing.
>
>
Hi Stephen,
Sorry for late reply. I was taking the whole week off last week. How's
the test going?
Thanks,
-Kai
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-02-27 7:38 ` Huang, Kai
@ 2017-03-13 14:58 ` fangying
2017-03-13 16:57 ` Paolo Bonzini
0 siblings, 1 reply; 12+ messages in thread
From: fangying @ 2017-03-13 14:58 UTC (permalink / raw)
To: Huang, Kai, Herongguang (Stephen),
Paolo Bonzini, Chris Friesen, Han, Huaitong, hangaohuai, stable
Cc: kvm, xudong.hao, qemu-devel, wangxinxin.wang, rkrcmar,
guangrong.xiao, linux-kernel
Hi, Huang Kai
After weeks of intensive testing, we think the problem is solved and
this issue can be closed.
On 2017/2/27 15:38, Huang, Kai wrote:
>
>
> On 2/25/2017 2:44 PM, Herongguang (Stephen) wrote:
>>
>>
>> On 2017/2/24 23:14, Paolo Bonzini wrote:
>>>
>>>
>>> On 24/02/2017 16:10, Chris Friesen wrote:
>>>> On 02/23/2017 08:23 PM, Herongguang (Stephen) wrote:
>>>>
>>>>> On 2017/2/22 22:43, Paolo Bonzini wrote:
>>>>
>>>>>> Hopefully Gaohuai and Rongguang can help with this too.
>>>>>>
>>>>>> Paolo
>>>>>
>>>>> Yes, we are looking into and testing this.
>>>>>
>>>>> I think this can result in any memory corruption, if VM1 writes its
>>>>> PML buffer into VM2’s VMCS (since sched_in/sched_out notifier of VM1
>>>>> is not registered yet), then VM1 is destroyed (hence its PML buffer
>>>>> is freed back to kernel), after that, VM2 starts migration, so CPU
>>>>> logs VM2’s dirty GFNS into a freed memory, results in any memory
>>>>> corruption.
>>>>>
>>>>> As its severity, this commit
>>>>> (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec)
>>>>>
>>>>>
>>>>>
>>>>> is eligible to back port to kernel stable.
>>>>
>>>> Are we expecting that fix to resolve the original issue, or is it a
>>>> separate issue that needs fixing in stable?
>>>
>>> It should be the original issue.
>>>
>>> Paolo
>>>
>>> .
>>>
>> Yes, I agree, though we are still testing.
>>
>>
> Hi Stephen,
>
> Sorry for late reply. I was taking the whole week off last week. How's
> the test going?
>
> Thanks,
> -Kai
>
> .
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-03-13 14:58 ` fangying
@ 2017-03-13 16:57 ` Paolo Bonzini
2017-03-16 1:40 ` Huang, Kai
0 siblings, 1 reply; 12+ messages in thread
From: Paolo Bonzini @ 2017-03-13 16:57 UTC (permalink / raw)
To: fangying, Huang, Kai, Herongguang (Stephen),
Chris Friesen, Han, Huaitong, hangaohuai, stable
Cc: kvm, xudong.hao, qemu-devel, wangxinxin.wang, rkrcmar,
guangrong.xiao, linux-kernel
On 13/03/2017 15:58, fangying wrote:
> Hi, Huang Kai
>
> After weeks of intensive testing, we think the problem is solved and
> this issue can be closed.
Thanks for the update. We got to the same conclusion.
Paolo
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
2017-03-13 16:57 ` Paolo Bonzini
@ 2017-03-16 1:40 ` Huang, Kai
0 siblings, 0 replies; 12+ messages in thread
From: Huang, Kai @ 2017-03-16 1:40 UTC (permalink / raw)
To: Paolo Bonzini, fangying, Herongguang (Stephen),
Chris Friesen, Han, Huaitong, hangaohuai, stable
Cc: kvm, xudong.hao, qemu-devel, wangxinxin.wang, rkrcmar,
guangrong.xiao, linux-kernel
Thanks!
Thanks,
-Kai
On 3/14/2017 5:57 AM, Paolo Bonzini wrote:
>
>
> On 13/03/2017 15:58, fangying wrote:
>> Hi, Huang Kai
>>
>> After weeks of intensive testing, we think the problem is solved and
>> this issue can be closed.
>
> Thanks for the update. We got to the same conclusion.
>
> Paolo
>
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2017-03-16 1:40 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <589C7E96.9060905@huawei.com>
[not found] ` <589D83CE.1090803@huawei.com>
[not found] ` <589DDC05.9010807@windriver.com>
[not found] ` <58AA51D6.6020508@huawei.com>
[not found] ` <1487565495.3740.27.camel@intel.com>
[not found] ` <58AD0094.90304@windriver.com>
[not found] ` <4dd92012-626a-2d80-9adb-0be398f73eb1@redhat.com>
[not found] ` <58AD92AE.6040502@windriver.com>
[not found] ` <6c5567f4-192d-aefd-90e4-89f53479c24e@redhat.com>
2017-02-24 2:23 ` [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration Herongguang (Stephen)
2017-02-24 9:35 ` Herongguang (Stephen)
2017-02-24 9:59 ` Greg KH
2017-02-24 10:00 ` Paolo Bonzini
2017-02-24 10:07 ` Greg KH
2017-02-24 15:10 ` Chris Friesen
2017-02-24 15:14 ` Paolo Bonzini
2017-02-25 1:44 ` Herongguang (Stephen)
2017-02-27 7:38 ` Huang, Kai
2017-03-13 14:58 ` fangying
2017-03-13 16:57 ` Paolo Bonzini
2017-03-16 1:40 ` Huang, Kai
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).