Bug 1224243 - xlators: fix allocation of zero bytes
Summary: xlators: fix allocation of zero bytes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Prasanna Kumar Kalever
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-22 11:18 UTC by Prasanna Kumar Kalever
Modified: 2018-08-29 03:34 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.1.3 (or later)
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-29 03:34:50 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.