Re: [PATCH net-next] sctp: change sk state to CLOSED instead of CLOSING in sctp_sock_migrate

2016-06-16 Thread David Miller
From: marcelo.leit...@gmail.com Date: Thu, 16 Jun 2016 18:13:22 -0300 > On Thu, Jun 16, 2016 at 02:11:39PM -0700, David Miller wrote: >> From: Xin Long >> Date: Thu, 16 Jun 2016 01:15:06 +0800 >> >> > Commit d46e416c11c8 ("sctp: sctp should change socket state when >> >

Re: [PATCH net-next] sctp: change sk state to CLOSED instead of CLOSING in sctp_sock_migrate

2016-06-16 Thread marcelo . leitner
On Thu, Jun 16, 2016 at 02:11:39PM -0700, David Miller wrote: > From: Xin Long > Date: Thu, 16 Jun 2016 01:15:06 +0800 > > > Commit d46e416c11c8 ("sctp: sctp should change socket state when > > shutdown is received") may set sk_state CLOSING in sctp_sock_migrate, > > but

Re: [PATCH net-next] sctp: change sk state to CLOSED instead of CLOSING in sctp_sock_migrate

2016-06-16 Thread David Miller
From: Xin Long Date: Thu, 16 Jun 2016 01:15:06 +0800 > Commit d46e416c11c8 ("sctp: sctp should change socket state when > shutdown is received") may set sk_state CLOSING in sctp_sock_migrate, > but inet_accept doesn't allow the sk_state other than ESTABLISHED/ > CLOSED for

Re: [PATCH net-next] sctp: change sk state to CLOSED instead of CLOSING in sctp_sock_migrate

2016-06-15 Thread Sergei Shtylyov
Hello. On 06/15/2016 08:15 PM, Xin Long wrote: Commit d46e416c11c8 ("sctp: sctp should change socket state when shutdown is received") may set sk_state CLOSING in sctp_sock_migrate, but inet_accept doesn't allow the sk_state other than ESTABLISHED/ CLOSED for sctp. So we will change sk_state

[PATCH net-next] sctp: change sk state to CLOSED instead of CLOSING in sctp_sock_migrate

2016-06-15 Thread Xin Long
Commit d46e416c11c8 ("sctp: sctp should change socket state when shutdown is received") may set sk_state CLOSING in sctp_sock_migrate, but inet_accept doesn't allow the sk_state other than ESTABLISHED/ CLOSED for sctp. So we will change sk_state to CLOSED, instead of CLOSING, as actually sk is