Details
-
Technical task
-
Resolution: Fixed
-
Major
-
Lustre 2.4.0, Lustre 2.1.3
-
4437
Description
Thanks to the Coverity tool, we found some resource leak errors in the Lustre code. This is typically what happens when a function forgets to free some allocated memory or close some file descriptor while returning in case of error.
I will propose a patch to address the issues.
Yes but we can link tickets together and avoid possible support confusion. The original reported issue was fixed in 2.3. Reopening this ticket in relation to code landed after 2.3 might suggest otherwise.