On 06/13/2017 09:26 AM, Michal Privoznik wrote:
> On 06/13/2017 02:35 PM, John Ferlan wrote:
>>
>>
>> On 06/13/2017 07:31 AM, Michal Privoznik wrote:
>>> On 06/12/2017 11:26 PM, John Ferlan wrote:
On 06/05/2017 04:22 AM, Michal Privoznik wrote:
> When the I/O thread quits
On 06/13/2017 02:35 PM, John Ferlan wrote:
>
>
> On 06/13/2017 07:31 AM, Michal Privoznik wrote:
>> On 06/12/2017 11:26 PM, John Ferlan wrote:
>>>
>>>
>>> On 06/05/2017 04:22 AM, Michal Privoznik wrote:
When the I/O thread quits (e.g. due to an I/O error, lseek()
error, whatever), any
On 06/13/2017 07:31 AM, Michal Privoznik wrote:
> On 06/12/2017 11:26 PM, John Ferlan wrote:
>>
>>
>> On 06/05/2017 04:22 AM, Michal Privoznik wrote:
>>> When the I/O thread quits (e.g. due to an I/O error, lseek()
>>> error, whatever), any subsequent virFDStream API should return
>>> error too.
On 06/12/2017 11:26 PM, John Ferlan wrote:
>
>
> On 06/05/2017 04:22 AM, Michal Privoznik wrote:
>> When the I/O thread quits (e.g. due to an I/O error, lseek()
>> error, whatever), any subsequent virFDStream API should return
>> error too. Moreover, when invoking stream event callback, we must
On 06/05/2017 04:22 AM, Michal Privoznik wrote:
> When the I/O thread quits (e.g. due to an I/O error, lseek()
> error, whatever), any subsequent virFDStream API should return
> error too. Moreover, when invoking stream event callback, we must
> set the VIR_STREAM_EVENT_ERROR flag so that the
When the I/O thread quits (e.g. due to an I/O error, lseek()
error, whatever), any subsequent virFDStream API should return
error too. Moreover, when invoking stream event callback, we must
set the VIR_STREAM_EVENT_ERROR flag so that the callback knows
something bad happened.
Signed-off-by: