RE: [PATCH] VSOCK: bind to random port for VMADDR_PORT_ANY

2018-12-12 Thread Dexuan Cui
> From: Stefan Hajnoczi > Sent: Tuesday, December 11, 2018 8:27 AM > To: Jorgen Hansen ; Dexuan Cui > > Cc: netdev@vger.kernel.org; Lepton Wu > Subject: Re: [PATCH] VSOCK: bind to random port for VMADDR_PORT_ANY > > On Mon, Dec 10, 2018 at 11:02:35PM -0800, Lepton Wu

Re: [PATCH] VSOCK: bind to random port for VMADDR_PORT_ANY

2018-12-11 Thread Jorgen S. Hansen
> On Mon, Dec 10, 2018 at 11:02:35PM -0800, Lepton Wu wrote: > > The old code always starts from fixed port for VMADDR_PORT_ANY. Sometimes > > when VMM crashed, there is still orphaned vsock which is waiting for > > close timer, then it could cause connection time out for new started VM > > if th

Re: [PATCH] VSOCK: bind to random port for VMADDR_PORT_ANY

2018-12-11 Thread Stefan Hajnoczi
On Mon, Dec 10, 2018 at 11:02:35PM -0800, Lepton Wu wrote: > The old code always starts from fixed port for VMADDR_PORT_ANY. Sometimes > when VMM crashed, there is still orphaned vsock which is waiting for > close timer, then it could cause connection time out for new started VM > if they are tryin

[PATCH] VSOCK: bind to random port for VMADDR_PORT_ANY

2018-12-10 Thread Lepton Wu
The old code always starts from fixed port for VMADDR_PORT_ANY. Sometimes when VMM crashed, there is still orphaned vsock which is waiting for close timer, then it could cause connection time out for new started VM if they are trying to connect to same port with same guest cid since the new packets