Bug 763202 (GLUSTER-1470) - The forced alignment that breaks dict serialization in ARM v5tel (eg XScale) has not been fixed in Gluster v2 yet.
Summary: The forced alignment that breaks dict serialization in ARM v5tel (eg XScale) ...
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-1470
Product: GlusterFS
Classification: Community
Component: unclassified
Version: 2.0.9
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL: http://bugs.gluster.com/cgi-bin/bugzi...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-28 21:36 UTC by Ted Bagg
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Inlines the four-byte memcpy needed in dict_unserialize() & _dict_serialize(). (2.03 KB, patch)
2010-08-28 18:36 UTC, Ted Bagg 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Ted Bagg 2010-08-28 21:36:45 UTC 
This was reported as Bug 397 and was fixed in v3.0.0, I believe.  But the fix has not been applied to v2 as of 2.0.9, the current stable branch at the time of this report.  My company must use v2 for the moment as we need compatibility with Mac clients.

Moreover, fix supplied in 3.0.0 is inefficient on an ARM because memcpy() is not inlined there in gcc -g -O2.  I've attached a better fix below for 2.0.9 which should be no slower on most other architectures.  Companion patches will be supplied in a related entry for v3, where the corresponding revision is an enhancement rather than a repair.
Comment 1 Vijay Bellur 2010-08-30 03:28:45 UTC 
Downgrading severity as it affects specific platforms.
Comment 2 Amar Tumballi 2010-10-05 05:54:04 UTC 
We will work on only x86_* arch for the 3.1.0, will take it in 3.1.x version
Comment 3 Amar Tumballi 2011-01-21 07:50:34 UTC 
With the current codebase, this bug is invalid, as we have fixed the issues with architecture dependent code. Please use 3.1.x version.
Note You need to log in before you can comment on or make changes to this bug.