Description of problem: While using libgfapi-python bindings, a "None" passed as volname would translate to NULL being passed to glfs_new(). This causes segfault. Expected results: glfs_new() should error out gracefully with errno set to EINVAL.
REVIEW: http://review.gluster.org/9735 (gfapi: Add NULL check for volname in glfs_new()) posted (#5) for review on master by Prashanth Pai (ppai)
COMMIT: http://review.gluster.org/9735 committed in master by Niels de Vos (ndevos) ------ commit 9b3c799fa3a5535e189d18200324d912339ac6a6 Author: Prashanth Pai <ppai> Date: Tue Feb 24 16:48:20 2015 +0530 gfapi: Add NULL check for volname in glfs_new() BUG: 1199388 Change-Id: I66cb65355504eb47e4392576029a9a5422996a1b Signed-off-by: Prashanth Pai <ppai> Reviewed-on: http://review.gluster.org/9735 Reviewed-by: Shyamsundar Ranganathan <srangana> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user