diff options
| author | Jon Paul Maloy | 2014-07-11 14:45:27 +0200 |
|---|---|---|
| committer | David S. Miller | 2014-07-12 00:02:10 +0200 |
| commit | 999417549c16dd0e3a382aa9f6ae61688db03181 (patch) | |
| tree | bc6c9abeee8bf65d9785cc9b867e39aab7754729 /drivers/net | |
| parent | r8152: fix r8152_csum_workaround function (diff) | |
| download | kernel-qcow2-linux-999417549c16dd0e3a382aa9f6ae61688db03181.tar.gz kernel-qcow2-linux-999417549c16dd0e3a382aa9f6ae61688db03181.tar.xz kernel-qcow2-linux-999417549c16dd0e3a382aa9f6ae61688db03181.zip | |
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 40ba3cdf542a469aaa9083fa041656e59b109b90 ("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>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions