Support to distinguish locks set via clients using SYNCOP framework

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Server lock xlator seems to be distinguishing the various locks set by the clients on a file using two parameters -

* client UUID
* frame->root->lk_owner

Hence if it is the same client setting locks on a file, for the server to treat them as being from different owners, the client need to pass different lk_owners(as 'frame->root->lk_owner') for all those locks.

At present FUSE and gluster-nfs set this field while creating the frame whereas this support is missing for the clients using the SYNCOP framework.

Have made the changes to fix the same. In addition have added an API in gfapi to pass the lk_owner to syncopctx.

http://review.gluster.org/#/c/9482/

Kindly review the changes.

Thanks,
Soumya
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux