Description of problem: When an unprivileged user (one without cap_net_bind_service capability) tries to connect to a volume using RDMA transport (tested using libgfapi) the client hangs trying to bind a privileged port. This happenes because when failing to bind a privileged port because of EACCES, rdma_bind_addr is never called on the fall-through unprivileged port. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Use libgfapi to mount a volume as an unprivileged user using rdma transport. Actual results: Hang trying to bind local port. Expected results: Successfully mount the volume. Additional info:
REVIEW: http://review.gluster.org/9737 (rdma: Fix failure to call rdma_bind_addr if unable to bind privileged port.) posted (#1) for review on master by Mark Lipscombe (mlipscombe)
REVIEW: http://review.gluster.org/9737 (rdma: Fix failure to call rdma_bind_addr if unable to bind privileged port.) posted (#2) for review on master by Mark Lipscombe (mlipscombe)
REVIEW: http://review.gluster.org/9737 (rdma: Fix failure to call rdma_bind_addr if unable to bind privileged port.) posted (#3) for review on master by Mark Lipscombe (mlipscombe)
REVIEW: http://review.gluster.org/9737 (rdma: Fix failure to call rdma_bind_addr if unable to bind privileged port.) posted (#4) for review on master by Mark Lipscombe (mlipscombe)
COMMIT: http://review.gluster.org/9737 committed in master by Raghavendra G (rgowdapp) ------ commit 0e3fd04e93b163f27ecbea4a3a777c041b4352b4 Author: Mark Lipscombe <mlipscombe> Date: Tue Feb 24 12:28:27 2015 -0800 rdma: Fix failure to call rdma_bind_addr if unable to bind privileged port. When unable to bind a privileged port, rdma_bind_addr is not called. This patch fixes that. Change-Id: I175884a5d6a08b93dc62653ee0a6622bfc06e618 Bug: 1195907 Signed-off-by: Mark Lipscombe <mlipscombe> Reviewed-on: http://review.gluster.org/9737 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: mohammed rafi kc <rkavunga> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
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