• Erik Hugne's avatar
    tipc: don't reroute message fragments · 528f6f4b
    Erik Hugne authored
    When a message fragment is received in a broadcast or unicast link,
    the reception code will append the fragment payload to a big reassembly
    buffer through a call to the function tipc_recv_fragm(). However, after
    the return of that call, the logics goes on and passes the fragment
    buffer to the function tipc_net_route_msg(), which will simply drop it.
    This behavior is a remnant from the now obsolete multi-cluster
    functionality, and has no relevance in the current code base.
    
    Although currently harmless, this unnecessary call would be fatal
    after applying the next patch in this series, which introduces
    a completely new reassembly algorithm. So we change the code to
    eliminate the redundant call.
    Signed-off-by: default avatarErik Hugne <erik.hugne@ericsson.com>
    Reviewed-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
    Signed-off-by: default avatarJon Maloy <jon.maloy@ericsson.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    528f6f4b
link.c 75.7 KB