Searched hist:"7 efea60dcffc151870d1abbfccdb1f11cd4b7f21" (Results 1 – 3 of 3) sorted by relevance
/linux/net/tipc/ |
H A D | subscr.h | diff 7efea60dcffc151870d1abbfccdb1f11cd4b7f21 Tue Mar 28 12:28:28 CEST 2017 Ying Xue <ying.xue@windriver.com> tipc: adjust the policy of holding subscription kref
When a new subscription object is inserted into name_seq->subscriptions list, it's under name_seq->lock protection; when a subscription is deleted from the list, it's also under the same lock protection; similarly, when accessing a subscription by going through subscriptions list, the entire process is also protected by the name_seq->lock.
Therefore, if subscription refcount is increased before it's inserted into subscriptions list, and its refcount is decreased after it's deleted from the list, it will be unnecessary to hold refcount at all before accessing subscription object which is obtained by going through subscriptions list under name_seq->lock protection.
Signed-off-by: Ying Xue <ying.xue@windriver.com> Reviewed-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | subscr.c | diff 7efea60dcffc151870d1abbfccdb1f11cd4b7f21 Tue Mar 28 12:28:28 CEST 2017 Ying Xue <ying.xue@windriver.com> tipc: adjust the policy of holding subscription kref
When a new subscription object is inserted into name_seq->subscriptions list, it's under name_seq->lock protection; when a subscription is deleted from the list, it's also under the same lock protection; similarly, when accessing a subscription by going through subscriptions list, the entire process is also protected by the name_seq->lock.
Therefore, if subscription refcount is increased before it's inserted into subscriptions list, and its refcount is decreased after it's deleted from the list, it will be unnecessary to hold refcount at all before accessing subscription object which is obtained by going through subscriptions list under name_seq->lock protection.
Signed-off-by: Ying Xue <ying.xue@windriver.com> Reviewed-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | name_table.c | diff 7efea60dcffc151870d1abbfccdb1f11cd4b7f21 Tue Mar 28 12:28:28 CEST 2017 Ying Xue <ying.xue@windriver.com> tipc: adjust the policy of holding subscription kref
When a new subscription object is inserted into name_seq->subscriptions list, it's under name_seq->lock protection; when a subscription is deleted from the list, it's also under the same lock protection; similarly, when accessing a subscription by going through subscriptions list, the entire process is also protected by the name_seq->lock.
Therefore, if subscription refcount is increased before it's inserted into subscriptions list, and its refcount is decreased after it's deleted from the list, it will be unnecessary to hold refcount at all before accessing subscription object which is obtained by going through subscriptions list under name_seq->lock protection.
Signed-off-by: Ying Xue <ying.xue@windriver.com> Reviewed-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|