Re: [net 1/1] tipc: avoid inheriting msg_non_seq flag when message is returned

2017-08-14 Thread David Miller
From: Jon Maloy Date: Mon, 14 Aug 2017 18:28:49 +0200 > In the function msg_reverse(), we reverse the header while trying to > reuse the original buffer whenever possible. Those rejected/returned > messages are always transmitted as unicast, but the msg_non_seq field > is not explicitly set to ze

[net 1/1] tipc: avoid inheriting msg_non_seq flag when message is returned

2017-08-14 Thread Jon Maloy
In the function msg_reverse(), we reverse the header while trying to reuse the original buffer whenever possible. Those rejected/returned messages are always transmitted as unicast, but the msg_non_seq field is not explicitly set to zero as it should be. We have seen cases where multicast senders