tipc: same receive code path for connection protocol and data messages
As a preparation to eliminate port_lock we need to bring reception of connection protocol messages under proper protection of bh_lock_sock or socket owner. We fix this by letting those messages follow the same code path as incoming data messages. As a side effect of this change, the last reference to the function net_route_msg() disappears, and we can eliminate that function. Signed-off-by: Jon Maloy <jon.maloy@ericsson.com> Reviewed-by: Erik Hugne <erik.hugne@ericsson.com> Reviewed-by: Ying Xue <ying.xue@windriver.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
committed by
David S. Miller
parent
b786e2b0fa
commit
ec8a2e5621
@@ -140,7 +140,7 @@ int tipc_port_mcast_xmit(struct tipc_port *port,
|
||||
unsigned int len);
|
||||
|
||||
struct sk_buff *tipc_port_get_ports(void);
|
||||
void tipc_port_proto_rcv(struct sk_buff *buf);
|
||||
void tipc_port_proto_rcv(struct tipc_port *port, struct sk_buff *buf);
|
||||
void tipc_port_mcast_rcv(struct sk_buff *buf, struct tipc_port_list *dp);
|
||||
void tipc_port_reinit(void);
|
||||
|
||||
|
Reference in New Issue
Block a user