summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorVenky Shankar <vshankar@redhat.com>2015-06-04 10:07:38 +0530
committerRaghavendra Bhat <raghavendra@redhat.com>2015-06-19 01:37:54 -0700
commitc79977c23f6108128043986995fe2eacf35dc6ac (patch)
treeb70eea13da244881b2fa4d427d9339f9ec01ee8c /doc
parent2f027e49f4105289eb7455964eec29349bbdbf34 (diff)
features/bitrot: fix fd leak in truncate (stub)
Backport of http://review.gluster.org/#/c/11077 The need to perform object versioning in the truncate() code path required an fd to reuse existing versioning infrastructure that's used by fd based operations (such as writev(), ftruncate(), etc..). This tempted the use of anonymous fd which was never ever unref()'d after use resulting in fd and/or memory leak depending on the code path taken. Versioning resulted in a dangling file descriptor left open in the filesystem effecting the signing process of a given object (no release() would be trigerred, hence no signing would be performed). On the other hand, cases where the object need not be versioned, the anonymous fd in still ref()'d resulting in memory leak (NOTE: there's no "dangling" file descriptor in this case). Change-Id: I29c3d2af9bbc5cd4b8ddf38954080e3c7a44ba61 BUG: 1232179 Signed-off-by: Venky Shankar <vshankar@redhat.com> Reviewed-on: http://review.gluster.org/11300 Tested-by: Gluster Build System <jenkins@build.gluster.com> Tested-by: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions