Re: [PATCH net-next 2/5] sctp: apply rhashtable api to send/recv path

2016-01-06 Thread Xin Long
On Wed, Jan 6, 2016 at 3:07 AM, Vlad Yasevich wrote: > On 12/30/2015 10:50 AM, Xin Long wrote: >> apply lookup apis to two functions, for __sctp_endpoint_lookup_assoc >> and __sctp_lookup_association, it's invoked in the protection of sock >> lock, it will be safe, but

Re: [PATCH net-next 2/5] sctp: apply rhashtable api to send/recv path

2016-01-06 Thread mleitner
On Tue, Jan 05, 2016 at 02:07:11PM -0500, Vlad Yasevich wrote: > On 12/30/2015 10:50 AM, Xin Long wrote: > > apply lookup apis to two functions, for __sctp_endpoint_lookup_assoc > > and __sctp_lookup_association, it's invoked in the protection of sock > > lock, it will be safe, but

Re: [PATCH net-next 2/5] sctp: apply rhashtable api to send/recv path

2016-01-05 Thread Vlad Yasevich
On 12/30/2015 10:50 AM, Xin Long wrote: > apply lookup apis to two functions, for __sctp_endpoint_lookup_assoc > and __sctp_lookup_association, it's invoked in the protection of sock > lock, it will be safe, but sctp_lookup_association need to call > rcu_read_lock() and to detect the t->dead to

[PATCH net-next 2/5] sctp: apply rhashtable api to send/recv path

2015-12-30 Thread Xin Long
apply lookup apis to two functions, for __sctp_endpoint_lookup_assoc and __sctp_lookup_association, it's invoked in the protection of sock lock, it will be safe, but sctp_lookup_association need to call rcu_read_lock() and to detect the t->dead to protect it. Signed-off-by: Xin Long