diff options
author | Michael J. Ruhl <[email protected]> | 2017-05-04 05:14:34 -0700 |
---|---|---|
committer | Doug Ledford <[email protected]> | 2017-05-04 19:31:46 -0400 |
commit | 224d71f910102c966cdcd782c97e096d5e26e4da (patch) | |
tree | 50184af1bae4d0dc5af6b52ccb51a396431d6ec2 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 94679061dcdddbafcf24e3bfb526e54dedcc2f2f (diff) |
IB/hfi1: Fix a subcontext memory leak
The only context that frees user_exp_rcv data structures is the last
context closed (from a sub-context set). This leaks the allocations
from the other sub-contexts. Separate the common frees from the
specific frees and call them at the appropriate time.
Using KEDR to check for memory leaks we get:
Before test:
[leak_check] Possible leaks: 25
After test:
[leak_check] Possible leaks: 31 (6 leaked data structures)
After patch applied (before and after test have the same value)
[leak_check] Possible leaks: 25
Each leak is 192 + 13440 + 6720 = 20352 bytes per sub-context.
Cc: [email protected]
Reviewed-by: Mike Marciniszyn <[email protected]>
Signed-off-by: Michael J. Ruhl <[email protected]>
Signed-off-by: Dennis Dalessandro <[email protected]>
Signed-off-by: Doug Ledford <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions