[PATCH 4/6 net-next] inet: don't check for bind conflicts twice when searching for a port

2017-01-17 Thread Josef Bacik
This is just wasted time, we've already found a tb that doesn't have a bind conflict, and we don't drop the head lock so scanning again isn't going to give us a different answer. Instead move the tb->reuse setting logic outside of the found_tb path and put it in the success: path. Then make it

[PATCH 4/6 net-next] inet: don't check for bind conflicts twice when searching for a port

2017-01-11 Thread Josef Bacik
This is just wasted time, we've already found a tb that doesn't have a bind conflict, and we don't drop the head lock so scanning again isn't going to give us a different answer. Instead move the tb->reuse setting logic outside of the found_tb path and put it in the success: path. Then make it

Re: [PATCH 4/6 net-next] inet: don't check for bind conflicts twice when searching for a port

2016-12-23 Thread David Miller
From: Josef Bacik Date: Thu, 22 Dec 2016 16:26:36 -0500 > This is just wasted time, we've already found a tb that doesn't have a bind > conflict, and we don't drop the head lock so scanning again isn't going to > give > us a different answer. Instead move the tb->reuse setting

[PATCH 4/6 net-next] inet: don't check for bind conflicts twice when searching for a port

2016-12-22 Thread Josef Bacik
This is just wasted time, we've already found a tb that doesn't have a bind conflict, and we don't drop the head lock so scanning again isn't going to give us a different answer. Instead move the tb->reuse setting logic outside of the found_tb path and put it in the success: path. Then make it