Description of problem: The recent changes to use malloc instead of calloc left the strings new_name and new_path non-null terminated because they were initialised using strncpy. Use snprintf instead to make sure they are NULL terminated. 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/21112 (dht: Use snprintf instead of strncpy) posted (#1) for review on master by N Balachandran
COMMIT: https://review.gluster.org/21112 committed in master by "Amar Tumballi" <amarts> with a commit message- dht: Use snprintf instead of strncpy The recent changes to use malloc instead of calloc left the new_name and new_path non-null terminated. We now use snprintf instead of strncpy to fix this. Change-Id: I1a31701ca9447efde38921be0ba2c73cde2e7976 fixes: bz#1626346 Signed-off-by: N Balachandran <nbalacha>
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-5.0, please open a new bug report. glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/