+++ This bug was initially created as a clone of Bug #1412489 +++
Description of problem:
In __upcall_inode_ctx_set() if __inode_ctx_set() fails, we should be freeing the allocated inode_ctx. That's not the case now. Thanks Nithya for the pointer.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Worker Ant on 2017-01-12 03:53:34 EST ---
REVIEW: http://review.gluster.org/16381 (Upcall: Fix possible memleak when inode_ctx_set fails) posted (#1) for review on master by soumya k (email@example.com)
--- Additional comment from Worker Ant on 2017-01-12 10:47:27 EST ---
COMMIT: http://review.gluster.org/16381 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: Soumya Koduri <email@example.com>
Date: Thu Jan 12 14:19:31 2017 +0530
Upcall: Fix possible memleak when inode_ctx_set fails
In __upcall_inode_ctx_set(), if inode_ctx_set fails we should
free allocated memory for ctx. This patch takes care of the same.
Reported-by: Nithya Balachandran <firstname.lastname@example.org>
Signed-off-by: Soumya Koduri <email@example.com>
Reviewed-by: N Balachandran <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
REVIEW: http://review.gluster.org/16430 (Upcall: Fix possible memleak when inode_ctx_set fails) posted (#1) for review on release-3.9 by soumya k (email@example.com)
This bug is getting closed because GlusterFS-3.9 has reached its end-of-life .
Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please open a new bug against the newer release.