linux/net/tipc
Jon Paul Maloy 999417549c tipc: clear 'next'-pointer of message fragments before reassembly
If the 'next' pointer of the last fragment buffer in a message is not
zeroed before reassembly, we risk ending up with a corrupt message,
since the reassembly function itself isn't doing this.

Currently, when a buffer is retrieved from the deferred queue of the
broadcast link, the next pointer is not cleared, with the result as
described above.

This commit corrects this, and thereby fixes a bug that may occur when
long broadcast messages are transmitted across dual interfaces. The bug
has been present since 40ba3cdf54 ("tipc:
message reassembly using fragment chain")

This commit should be applied to both net and net-next.

Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2014-07-11 15:02:10 -07:00
..
Kconfig
Makefile
addr.c
addr.h
bcast.c tipc: clear 'next'-pointer of message fragments before reassembly 2014-07-11 15:02:10 -07:00
bcast.h
bearer.c
bearer.h
config.c
config.h
core.c
core.h
discover.c
discover.h
eth_media.c
ib_media.c
link.c tipc: merge port message reception into socket reception function 2014-05-14 15:19:48 -04:00
link.h
log.c
msg.c tipc: fix bug in multicast/broadcast message reassembly 2014-07-08 15:55:09 -07:00
msg.h
name_distr.c
name_distr.h
name_table.c
name_table.h
net.c tipc: merge port message reception into socket reception function 2014-05-14 15:19:48 -04:00
net.h
netlink.c
node.c
node.h
node_subscr.c
node_subscr.h
port.c tipc: merge port message reception into socket reception function 2014-05-14 15:19:48 -04:00
port.h tipc: merge port message reception into socket reception function 2014-05-14 15:19:48 -04:00
ref.c
ref.h
server.c
server.h
socket.c tipc: fix potential bug in function tipc_backlog_rcv 2014-06-11 15:01:30 -07:00
socket.h tipc: merge port message reception into socket reception function 2014-05-14 15:19:48 -04:00
subscr.c
subscr.h
sysctl.c