Description of problem: There is a function iov_lengh to calculate iovs total length, we can use this common function instead of other implementations in some xlators Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/16975 (coreutils: use coreutils instead of duplicate code) posted (#2) for review on master by Zhou Zhengping (johnzzpcrystal)
COMMIT: https://review.gluster.org/16975 committed in master by Jeff Darcy (jeff.us) ------ commit fe83a4ae84dd4345d6e958219d5a1dc59ecb039d Author: Zhou Zhengping <johnzzpcrystal> Date: Fri Mar 31 00:42:46 2017 +0800 coreutils: use coreutils instead of duplicate code Change-Id: I0e442331d2bbb22ec18c37af87ab2a8852737c43 BUG: 1448265 Signed-off-by: Zhou Zhengping <johnzzpcrystal> Reviewed-on: https://review.gluster.org/16975 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> Reviewed-by: Prashanth Pai <ppai> Reviewed-by: Jeff Darcy <jeff.us>
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.12.0, please open a new bug report. glusterfs-3.12.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-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/