nfs: Fix compiler warning when calling svc_getcaller Summary: - The result needs to be cast to (struct sockaddr_in *) - This diff is a cherry-pick of D3111554 to 3.8 Signed-off-by: Shreyas Siravara <sshreyas> Change-Id: If4c27dbe6c032f9e278ea08cd3c96a4d07bcc5f9 Reviewed-on: http://review.gluster.org/16179 Tested-by: Shreyas Siravara <sshreyas> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kevin Vigor <kvigor> CentOS-regression: Gluster Build System <jenkins.org>
REVIEW: https://review.gluster.org/16804 (nfs: Fix compiler warning when calling svc_getcaller) posted (#1) for review on master by Vijay Bellur (vbellur)
REVIEW: https://review.gluster.org/16804 (nfs: Fix compiler warning when calling svc_getcaller) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: https://review.gluster.org/16804 committed in master by Niels de Vos (ndevos) ------ commit 10a797c26f0e9db33b2b5b89263f6cca3709c002 Author: Kevin Vigor <kvigor> Date: Tue Mar 29 14:08:38 2016 -0700 nfs: Fix compiler warning when calling svc_getcaller Summary: When using libtirpc instead of glibc rpc the result needs to be cast to (struct sockaddr_in *) This diff was originally a cherry-pick of D3111554 to 3.8 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Signed-off-by: Shreyas Siravara <sshreyas> Change-Id: If4c27dbe6c032f9e278ea08cd3c96a4d07bcc5f9 BUG: 1428073 Reviewed-on: http://review.gluster.org/16179 Tested-by: Shreyas Siravara <sshreyas> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kevin Vigor <kvigor> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-on: https://review.gluster.org/16804 Reviewed-by: Amar Tumballi <amarts> 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.11.0, please open a new bug report. glusterfs-3.11.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://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/