Bug 1224243

Summary:	xlators: fix allocation of zero bytes
Product:	[Community] GlusterFS	Reporter:	Prasanna Kumar Kalever <prasanna.kalever>
Component:	core	Assignee:	Prasanna Kumar Kalever <prasanna.kalever>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	amukherj, bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.3 (or later)	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 03:34:50 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 Prasanna Kumar Kalever 2015-05-22 11:18:09 UTC

Description of problem:
Allocation of zero bytes with alloc() function

Version-Release number of selected component (if applicable):
Mainline

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2015-05-22 11:25:16 UTC

REVIEW: http://review.gluster.org/10891 (xlators: fix allocation of zero bytes) posted (#1) for review on master by Prasanna Kumar Kalever

Comment 2 Anand Avati 2015-05-22 11:28:29 UTC

REVIEW: http://review.gluster.org/10891 (xlators: fix allocation of zero bytes) posted (#2) for review on master by Prasanna Kumar Kalever

Comment 3 Anand Avati 2015-05-22 11:31:02 UTC

REVIEW: http://review.gluster.org/10891 (xlators: fix allocation of zero bytes) posted (#3) for review on master by Prasanna Kumar Kalever

Comment 4 Anand Avati 2015-05-25 07:25:42 UTC

REVIEW: http://review.gluster.org/10891 (xlators: fix allocation of zero bytes) posted (#4) for review on master by Prasanna Kumar Kalever

Comment 5 Mike McCune 2016-03-28 23:22:56 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 6 Amar Tumballi 2018-08-29 03:34:50 UTC

This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.