[LU-2053] Significant memory leak in new crypto code

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.3.0, Lustre 2.4.0
• Affects Version/s: Lustre 2.3.0, Lustre 2.4.0
• Severity: 3
• Assignee: Oleg Drokin
• Reporter: Oleg Drokin

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

[Oleg Drokin]

LAnded to b2_3 and cherrypicked to master

[Oleg Drokin]

Right, I had the same wrong assumption as you.
Though my (very limited) testing with leak tracing enabled did not find anything else.

[Andreas Dilger]

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.

[Oleg Drokin]

http://review.whamcloud.com/4135 is b2_3 version of the fix