Description of problem:
If xl->ctx is null, it can lead to segfault in xlator.c. In different code paths the ctx is getting adjusted, so we have to make sure the ctx is not null before proceeding.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The dereferencing operations can lead to segfault as the ctx is getting tainted at times in different paths.
There shouldnt be any crash because ctx being null.
REVIEW: http://review.gluster.org/9810 (xlator: avoiding possibility of a crash if (xl->ctx) is NULL.) posted (#1) for review on master by Humble Devassy Chirammal (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/9810 (xlator: avoiding possibility of a crash if (xl->ctx) is NULL.) posted (#2) for review on master by Humble Devassy Chirammal (email@example.com)
COMMIT: http://review.gluster.org/9810 committed in master by Vijay Bellur (firstname.lastname@example.org)
Author: Humble Devassy Chirammal <email@example.com>
Date: Wed Mar 4 18:38:07 2015 +0530
xlator: avoiding possibility of a crash if (xl->ctx) is NULL.
Signed-off-by: Humble Devassy Chirammal <firstname.lastname@example.org>.
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Raghavendra Bhat <firstname.lastname@example.org>
Reviewed-by: Vijay Bellur <email@example.com>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.