[Bugs] [Bug 1339226] New: gfapi: set mem_acct for the variables created for upcall
bugzilla at redhat.com
bugzilla at redhat.com
Tue May 24 12:28:11 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1339226
Bug ID: 1339226
Summary: gfapi: set mem_acct for the variables created for
upcall
Product: GlusterFS
Version: 3.7.11
Component: libgfapi
Keywords: Triaged
Severity: urgent
Assignee: bugs at gluster.org
Reporter: skoduri at redhat.com
QA Contact: sdharane at redhat.com
CC: bugs at gluster.org, sdharane at redhat.com
Depends On: 1339214
+++ This bug was initially created as a clone of Bug #1339214 +++
Description of problem:
In 'glfs_h_poll_cache_invalidation', we create a variable used 'up_inode_arg'
using calloc (which will not set any mem_acct info for that variable). But in
case of any errors during processing, we free it using 'GF_FREE' which makes
the process crash with ESEGV which trying to access mem_acct variables.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Create a 4 node ganesha cluster.
2. Create a volume and enable ganesha on it.
3. Mount the volume using vers=3 or 4 and create nested directories on the
mount point.
4. Add bricks to the volume.
gluster volume add-brick newvolume replica 2
5. start the rebalance process:
gluster v rebalance newvolume start force
6. Observe that while rebalance is in progress, ganesha process on the mounted
node gets killed with seg fault error:
Actual results:
nfs-ganesha process crashes with ESEGV
Expected results:
nfs-ganesha process shouldn't crash.
Additional info:
This issue is originally reported in bug1339208
--- Additional comment from Vijay Bellur on 2016-05-24 08:25:36 EDT ---
REVIEW: http://review.gluster.org/14521 (gfapi/upcall: Use GF_CALLOC while
allocating variables) posted (#1) for review on master by soumya k
(skoduri at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1339214
[Bug 1339214] gfapi: set mem_acct for the variables created for upcall
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list