Description of problem: A null pointer deref can occur in the error handling. Version-Release number of selected component (if applicable): How reproducible: Found by static analysis Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/20296 (cloudsync: avoid null pointer deref in error paths) posted (#1) for review on master by Thomas H.P. Andersen
COMMIT: https://review.gluster.org/20296 committed in master by "Amar Tumballi" <amarts> with a commit message- cloudsync: avoid null pointer deref in error paths In the case of OOM we would end up dereferencing priv in the out label of aws_init(). A similar deref would happen if a null priv is passed to aws_reconfigure(). Change-Id: I57c80aad2b52ecb1eda86a0077ed6b46816e5dea fixes: bz#1592141 Signed-off-by: Thomas Hindoe Paaboel Andersen <phomes>
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/