[LU-2053] Significant memory leak in new crypto code Created: 29/Sep/12 Updated: 01/Oct/12 Resolved: 01/Oct/12 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.3.0, Lustre 2.4.0 |
| Fix Version/s: | Lustre 2.3.0, Lustre 2.4.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Oleg Drokin | Assignee: | Oleg Drokin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 4295 |
| Description |
|
The new cryptoapi code introduced a memory allocation in cfs_crypto_hash_init for hdesc that's never freed anywhere other than on error path in cfs_crypto_hash_init itself. |
| Comments |
| Comment by Oleg Drokin [ 29/Sep/12 ] |
|
http://review.whamcloud.com/4135 is b2_3 version of the fix |
| Comment by Andreas Dilger [ 30/Sep/12 ] |
|
Strangely, I thought that cfs_alloc() has memory leak tracing, but it seems this is only true of OBD_ALLOC(). That means there is a real possibility of other memory leaks existing that we do not know about. |
| Comment by Oleg Drokin [ 01/Oct/12 ] |
|
Right, I had the same wrong assumption as you. |
| Comment by Oleg Drokin [ 01/Oct/12 ] |
|
LAnded to b2_3 and cherrypicked to master |