Bug 1386618

Summary: Fedora 23 NLM Server does not block a lock of a file which previously was locked by a different Lock Owner
Product: [Fedora] Fedora Reporter: radchenkoy
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: bcodding, bfields, jlayton, smayhew, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 21:39:12 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:
Attachments:
Description Flags
fedora 23, one ip, two lock owners
none
netapp, one ip, two lock owners none

Description radchenkoy 2016-10-19 10:05:25 UTC
Created attachment 1212102 [details]
fedora 23, one ip, two lock owners

Description of problem:

By using commercial NFS program I was able to send NLM lock requests on behalf of different lock owners
from the same client host.
I found inconsistent behavior of Fedora NLM Server with NetApp NLM Server.
 

// attached pcap file "fedora23_One_IP_Two_LockOwners.pcap" represent scenario with Fedora 23 NLM Server

37	0.019313	192.168.22.110	192.168.9.100	NLM	246	V4 LOCK Call (FH:0x07aa2ec4 Owner:LuisAlberto)
40	0.101989	192.168.9.100	192.168.22.110	NLM	94	V4 LOCK Reply

41	0.102140	192.168.22.110	192.168.9.100	NLM	246	V4 LOCK Call (FH:0x07aa2ec4 Owner:LuisAlberto2)
44	0.102648	192.168.9.100	192.168.22.110	NLM	94	V4 LOCK Reply


attached pcap file "netapp_One_IP_Two_LockOwners.pcap" represent scenario with NetApp NLM Server
46	1.051257	172.16.93.110	172.16.1.181	NLM	254	V4 LOCK Call  (FH:0x5a66b259 Owner:LuisAlberto)
47	1.051984	172.16.1.181	172.16.93.110	NLM	94	V4 LOCK Reply 

48	1.051999	172.16.93.110	172.16.1.181	NLM	254	V4 LOCK Call (FH:0x5a66b259 Owner:LuisAlberto2)
49	1.052627	172.16.1.181	172.16.93.110	NLM	94	V4 LOCK Reply NLM_BLOCKED

Second lock was granted by Fedora 23 NLM Server, but blocked by NetApp.
I think the behavior of NetApp server more suitable.

RHEL6.5 behaves like Fedora 23. 

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

Fedora 23, RHEL6.5

How reproducible:

I used commercial software from virtualinstruments, which allow to 
run several lock owners on one client host

Steps to Reproduce:
1.
2.
3.

Actual results:
Second lock was granted

Expected results:
Second lock should be blocked

Additional info:

Comment 1 radchenkoy 2016-10-19 10:06:50 UTC
Created attachment 1212103 [details]
netapp, one ip, two lock owners

Comment 2 Fedora End Of Life 2016-11-25 09:38:13 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2016-12-20 21:39:12 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.