Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1500669

Summary: nfs-ganesha: FSAL_CEPH appears to allow conflicting locks
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Ram Raja <rraja>
Component: CephFSAssignee: Jeff Layton <jlayton>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 3.0CC: anharris, ceph-eng-bugs, ceph-qe-bugs, dang, flucifre, jlayton, john.spray, mbenjamin, pdonnell, tserlin
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: nfs-ganesha-2.5.2-5.el7cp Ubuntu: nfs-ganesha_2.5.2-5redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:47:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ram Raja 2017-10-11 10:05:30 UTC 
Description of problem:

The upstream NFS-Ganesha bug in CephFS's FSAL,
https://github.com/nfs-ganesha/nfs-ganesha/issues/205

The problem described in the fix,
https://github.com/nfs-ganesha/nfs-ganesha/commit/d9f0536b7f3cbe6b9b4d0dc5b4e4acd3337d41b5

"If a lock is denied, the code will call getlk to get the conflicting lock info. That action then clobbers the return code and makes the lock appear to be a success."

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


How reproducible: Always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 18 Daniel Gryniewicz 2017-11-06 15:13:02 UTC 
These have been backported.
Comment 21 errata-xmlrpc 2017-12-05 23:47:58 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3387