+++ This bug was initially created as a clone of Bug #1499641 +++ Description of problem: Glusterfs server differentiates locks based on both client-id and lock owner. There is no provision to set lk_owner as of now via gfapi. Hence a new API is needed to set the same. Since the lk_owner is associated with a particular glfd (until we get mandatory lk support), the API definition looks like below - "glfd_set_lk_owner()" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Soumya Koduri on 2017-10-09 03:34:27 EDT --- https://review.gluster.org/#/c/18429 --- Additional comment from Worker Ant on 2017-10-09 06:06:12 EDT --- REVIEW: https://review.gluster.org/18429 (gfapi: set lkowner in glfd) posted (#3) for review on master by soumya k (skoduri) --- Additional comment from Worker Ant on 2017-10-10 07:57:54 EDT --- REVIEW: https://review.gluster.org/18429 (gfapi: set lkowner in glfd) posted (#4) for review on master by soumya k (skoduri) --- Additional comment from Worker Ant on 2017-10-12 06:42:51 EDT --- REVIEW: https://review.gluster.org/18429 (gfapi: set lkowner in glfd) posted (#5) for review on master by soumya k (skoduri) --- Additional comment from Worker Ant on 2017-10-13 03:48:04 EDT --- COMMIT: https://review.gluster.org/18429 committed in master by Niels de Vos (ndevos) ------ commit c22cec3928be6924fb1026ef969cae897efbd76d Author: Soumya Koduri <skoduri> Date: Wed Oct 4 14:34:48 2017 +0530 gfapi: set lkowner in glfd We need a provision to be able to set lkowner (which is used to distinguish locks maintained by server) in gfapi. Since the same lk_owner need to be used to be able to flush the lock while closing the fd, store the lkowner in the glfd structure itself. A new API has been added to be able to set lkowner in glfd. Change-Id: I67591d6b9a89c20b9617d52616513ff9e6c06b47 BUG: 1499641 Signed-off-by: Soumya Koduri <skoduri> --- Additional comment from Worker Ant on 2017-10-13 10:52:51 EDT --- REVIEW: https://review.gluster.org/18522 (gfapi: update symbol version of glfd_set_lkowner to 3.10.7) posted (#1) for review on master by soumya k (skoduri)
REVIEW: https://review.gluster.org/18523 (gfapi: set lkowner in glfd) posted (#1) for review on release-3.10 by soumya k (skoduri)
REVIEW: https://review.gluster.org/18523 (gfapi: set lkowner in glfd) posted (#2) for review on release-3.10 by soumya k (skoduri)
COMMIT: https://review.gluster.org/18523 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) ------ commit fea9e398da9865ce193d347d14fe2d56fe9946a2 Author: Soumya Koduri <skoduri> Date: Tue Oct 17 16:12:06 2017 +0530 gfapi: set lkowner in glfd We need a provision to be able to set lkowner (which is used to distinguish locks maintained by server) in gfapi. Since the same lk_owner need to be used to be able to flush the lock while closing the fd, store the lkowner in the glfd structure itself. A new API has been added to be able to set lkowner in glfd. This is backport of below mainline fix - https://review.gluster.org/#/c/18429 https://review.gluster.org/#/c/18522/ Change-Id: I67591d6b9a89c20b9617d52616513ff9e6c06b47 BUG: 1501955 Signed-off-by: Soumya Koduri <skoduri>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.7, please open a new bug report. glusterfs-3.10.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-November/000085.html [2] https://www.gluster.org/pipermail/gluster-users/