Bug 1430996 - Write-behind doesn't pass the application credentials while syncing cached writes
Summary: Write-behind doesn't pass the application credentials while syncing cached wr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: write-behind
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On: 1430608
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-10 05:13 UTC by Raghavendra G
Modified: 2019-07-02 04:12 UTC (History)
4 users (show)

Fixed In Version: glusterfs-6.x
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-02 04:12:21 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Raghavendra G 2017-03-10 05:13:43 UTC
Description of problem: It is not copying uid, pid, gid, ngroups, lk_owner, groups_large, groups, groups_small (various fields in call_stack/frame->root) etc during wb_fulfill. This is because wb_fulfill creates a new frame and a new frame created will have 0 set for all of these fields. This can result in various authentication mismatches by xlators like posix-acl etc. Note that these credentials have to be copied from frame->root to request as the original frame/call-stack might've been unwound and need not be alive at the time of wb_fulfill. One such issue can be seen in bz 1430608.

Another interesting fact to be looked at is that while collapsing multiple small writes into a single large holder, we should check for compatibility of these attributes across the requests that are collapsed.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Note You need to log in before you can comment on or make changes to this bug.