diff options
| author | Jon Paul Maloy <jon.maloy@ericsson.com> | 2014-06-25 20:41:30 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2014-06-27 12:50:54 -0700 |
| commit | 3d09fc424406b5610964507b3eb73cebbc3b4c38 (patch) | |
| tree | 7efb9664f22fa6cd8cb6fe361f7b4e9702943191 /net/tipc/socket.c | |
| parent | f5b265039f1381ec048a4d61d47130f71abb119b (diff) | |
| download | linux-stable-3d09fc424406b5610964507b3eb73cebbc3b4c38.tar.gz linux-stable-3d09fc424406b5610964507b3eb73cebbc3b4c38.tar.bz2 linux-stable-3d09fc424406b5610964507b3eb73cebbc3b4c38.zip | |
tipc: eliminate case of writing to freed memory
In the function tipc_nodesub_notify() we call a function pointer
aggregated into the object to be notified, whereafter we set
the function pointer to NULL. However, in some cases the function
pointed to will free the struct containing the function pointer,
resulting in a write to already freed memory.
This bug seems to always have been there, without causing any
notable harm.
In this commit we fix the problem by inverting the order of the
zeroing and the function call.
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc/socket.c')
0 files changed, 0 insertions, 0 deletions