Bug 1195907

Summary:	RDMA mount fails for unprivileged user without cap_net_bind_service
Product:	[Community] GlusterFS	Reporter:	Mark <mlipscombe>
Component:	rdma	Assignee:	Mark <mlipscombe>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, ndevos
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1196904 (view as bug list)		Environment:
Last Closed:	2015-05-14 17:29:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1196904

Description Mark 2015-02-24 20:42:31 UTC

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:

Comment 1 Anand Avati 2015-02-24 20:43:36 UTC

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)

Comment 2 Anand Avati 2015-02-25 05:35:06 UTC

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)

Comment 3 Anand Avati 2015-02-25 12:39:53 UTC

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)

Comment 4 Anand Avati 2015-02-25 13:51:04 UTC

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)

Comment 5 Anand Avati 2015-02-26 17:12:13 UTC

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>

Comment 6 Niels de Vos 2015-05-14 17:29:10 UTC

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

Comment 7 Niels de Vos 2015-05-14 17:35:51 UTC

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

Comment 8 Niels de Vos 2015-05-14 17:38:13 UTC

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

Comment 9 Niels de Vos 2015-05-14 17:46:00 UTC

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