Re: [PATCH] VSOCK: fix outdated sk_state value in hvs_release()

2017-12-05 Thread David Miller
From: Stefan Hajnoczi Date: Tue, 5 Dec 2017 11:31:14 + > Since commit 3b4477d2dcf2709d0be89e2a8dced3d0f4a017f2 ("VSOCK: use TCP > state constants for sk_state") VSOCK has used TCP_* constants for > sk_state. > > Commit b4562ca7925a3bedada87a3dd072dd5bad043288 ("hv_sock: add locking > in the

Re: [PATCH] VSOCK: fix outdated sk_state value in hvs_release()

2017-12-05 Thread Jorgen S. Hansen
> On Dec 5, 2017, at 12:31 PM, Stefan Hajnoczi wrote: > > Since commit 3b4477d2dcf2709d0be89e2a8dced3d0f4a017f2 ("VSOCK: use TCP > state constants for sk_state") VSOCK has used TCP_* constants for > sk_state. > > Commit b4562ca7925a3bedada87a3dd072dd5bad043288 ("hv_sock: add locking > in the op

[PATCH] VSOCK: fix outdated sk_state value in hvs_release()

2017-12-05 Thread Stefan Hajnoczi
Since commit 3b4477d2dcf2709d0be89e2a8dced3d0f4a017f2 ("VSOCK: use TCP state constants for sk_state") VSOCK has used TCP_* constants for sk_state. Commit b4562ca7925a3bedada87a3dd072dd5bad043288 ("hv_sock: add locking in the open/close/release code paths") reintroduced the SS_DISCONNECTING constan