Bug 951800 - AFR fops fail to propagate xdata
Summary: AFR fops fail to propagate xdata
Keywords:
Status: CLOSED DUPLICATE of bug 1021686
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-13 08:49 UTC by Prashanth Pai
Modified: 2014-07-13 07:08 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-13 07:08:09 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Prashanth Pai 2013-04-13 08:49:35 UTC 
AFR writev fop(and possibly many others) ignore xdata.

How to reproduce :
If xdata is set by a translator (in my case, the compression translator) located below AFR, AFR loses xdata.

What needs to be done in afr_writev (and others) : 

if(xdata)
   local->xdata_req = dict_ref(xdata);

and then pass local->xdata_req wherever STACK_WIND is called.
Comment 1 Anand Avati 2013-04-18 05:19:06 UTC 
REVIEW: http://review.gluster.org/4845 (afr: make writev not ignore xdata) posted (#1) for review on master by Prashanth Pai (nullpai)
Comment 2 Anand Avati 2013-04-18 06:41:49 UTC 
REVIEW: http://review.gluster.org/4845 (afr: make writev not ignore xdata) posted (#2) for review on master by Prashanth Pai (nullpai)
Comment 3 Jeff Darcy 2013-04-19 14:05:00 UTC 
This seems to be a problem with all fops, though the submitted patch only fixes writev (which is OK and appreciated).
Comment 4 Anand Avati 2013-08-12 07:31:16 UTC 
REVIEW: http://review.gluster.org/4845 (afr: make writev not ignore xdata) posted (#3) for review on master by Prashanth Pai (ppai)
Comment 5 Pranith Kumar K 2014-07-13 07:08:09 UTC 
This issue is addressed by refactor by Avati in http://review.gluster.org/6010. So closing this one.

*** This bug has been marked as a duplicate of bug 1021686 ***
Note You need to log in before you can comment on or make changes to this bug.