Bug 762764 (GLUSTER-1032) - Set lock-owner with pid when fuse does not supply value
Summary: Set lock-owner with pid when fuse does not supply value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1032
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: Linux
urgent
high
Target Milestone: ---
Assignee: Pavan Vilas Sondur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-27 16:25 UTC by Pavan Vilas Sondur
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Pavan Vilas Sondur 2010-06-27 16:25:56 UTC 
In afr transactions and self heal, some fops do not have frame->root->lk_owner set as FUSE does not set values for all FOPs. Set it with pid values to carry with sane lock-owner values for inodelks/entrylks.

Test Plan:
* Run posix test suite and turn on option 'option trace on' in locks xlator. All lk-owner values should have positive values (no zeros)

* Run self heal tests and verify non-zero lk-owner values just like described above.
Comment 1 Anand Avati 2010-06-29 06:58:07 UTC 
PATCH: http://patches.gluster.com/patch/3497 in release-3.0 (cluster/afr: Set lk-owner to pid when fuse does not supply it.)
Note You need to log in before you can comment on or make changes to this bug.