Bug 1500669 - nfs-ganesha: FSAL_CEPH appears to allow conflicting locks
Summary: nfs-ganesha: FSAL_CEPH appears to allow conflicting locks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: 3.0
Assignee: Jeff Layton
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-11 10:05 UTC by Ram Raja
Modified: 2017-12-05 23:47 UTC (History)
10 users (show)

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:
Clone Of:
Environment:
Last Closed: 2017-12-05 23:47:58 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github nfs-ganesha nfs-ganesha issues 205 0 None None None 2017-10-11 16:51:49 UTC
Red Hat Product Errata RHBA-2017:3387 0 normal SHIPPED_LIVE Red Hat Ceph Storage 3.0 bug fix and enhancement update 2017-12-06 03:03:45 UTC

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


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