Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1592141

Summary:	Null pointer deref in error paths
Product:	[Community] GlusterFS	Reporter:	Thomas H.P. Andersen <phomes>
Component:	unclassified	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:11:37 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:

Description Thomas H.P. Andersen 2018-06-17 19:07:18 UTC

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:

Comment 1 Worker Ant 2018-06-17 19:08:21 UTC

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

Comment 2 Worker Ant 2018-06-25 09:12:18 UTC

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>

Comment 3 Shyamsundar 2018-10-23 15:11:37 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-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/