Re: [PATCH v4 0/4] vsock: cancel connect packets when failing to connect

2017-01-17 Thread Jorgen S. Hansen
> On Jan 9, 2017, at 11:06 AM, Stefan Hajnoczi wrote: > > On Fri, Jan 06, 2017 at 10:22:56AM +0800, Peng Tao wrote: >> On Tue, Dec 13, 2016 at 5:50 PM, Stefan Hajnoczi wrote: >>> On Mon, Dec 12, 2016 at 08:21:05PM +0800, Peng Tao wrote: Currently,

Re: [PATCH v4 0/4] vsock: cancel connect packets when failing to connect

2017-01-11 Thread Stefan Hajnoczi
On Fri, Jan 06, 2017 at 10:22:56AM +0800, Peng Tao wrote: > On Tue, Dec 13, 2016 at 5:50 PM, Stefan Hajnoczi wrote: > > On Mon, Dec 12, 2016 at 08:21:05PM +0800, Peng Tao wrote: > >> Currently, if a connect call fails on a signal or timeout (e.g., guest is > >> still > >> in

Re: [PATCH v4 0/4] vsock: cancel connect packets when failing to connect

2017-01-05 Thread Peng Tao
On Tue, Dec 13, 2016 at 5:50 PM, Stefan Hajnoczi wrote: > On Mon, Dec 12, 2016 at 08:21:05PM +0800, Peng Tao wrote: >> Currently, if a connect call fails on a signal or timeout (e.g., guest is >> still >> in the process of starting up), we'll just return to caller and leave

Re: [PATCH v4 0/4] vsock: cancel connect packets when failing to connect

2016-12-13 Thread Stefan Hajnoczi
On Mon, Dec 12, 2016 at 08:21:05PM +0800, Peng Tao wrote: > Currently, if a connect call fails on a signal or timeout (e.g., guest is > still > in the process of starting up), we'll just return to caller and leave the > connect > packet queued and they are sent even though the connection is

[PATCH v4 0/4] vsock: cancel connect packets when failing to connect

2016-12-12 Thread Peng Tao
Currently, if a connect call fails on a signal or timeout (e.g., guest is still in the process of starting up), we'll just return to caller and leave the connect packet queued and they are sent even though the connection is considered a failure, which can confuse applications with unwanted false