RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 827846 - nfsd return unexpected code when conflicting delegation
Summary: nfsd return unexpected code when conflicting delegation
Keywords:
Status: CLOSED DUPLICATE of bug 823018
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: nfs-maint
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-03 09:20 UTC by Jian Li
Modified: 2014-03-04 00:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-04 03:47:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jian Li 2012-06-03 09:20:00 UTC
Description of problem:
When testing with pynfs, one of the case failed, IMO, the case try to break delegation, and got unexpected return code. I am testing on 2.6.32-277.el6.

> 564 def testLink(t, env):
> 565     """DELEGATION test
> 566
> 567     Get read delegation, then ensure LINK recalls it.
> 568     Respond properly and send DELEGRETURN.
> 569
> 570     FLAGS: delegations
> 571     CODE: DELEG15b
> 572     """
> 573     c = env.c1
> 574     count = c.cb_server.opcounts[OP_CB_RECALL]
> 575     c.init_connection('pynfs%i_%s' % (os.getpid(), t.code), cb_ident=0)
> 576     _get_deleg(t, c, c.homedir + [t.code], _recall, NFS4_OK)
> 577     ops = c.use_obj(c.homedir + [t.code]) + [c.savefh_op()];
> 578     ops += c.use_obj(c.homedir) + [c.link_op(t.code + '.link')];
> 579     _retry_conflicting_op(env, c, ops, "link")   #after got write delegation, link operation breaks the delegation on server. and NFSERR_OK or NFSERR_DELAY should be returned, in fact, NFSERR_NOENT is returned.
> 580     _verify_cb_occurred(t, c, count)
>
> test result:
> **************************************************
> DELEG15b st_delegation.testLink                                   : FAILURE
>            link which causes recall should return NFS4_OK or
>            NFS4ERR_DELAY, instead got NFS4ERR_NOENT
> **************************************************
>
> detailed result:
> COMPOUND4args(tag='', minorversion=0, argarray=[nfs_argop4(argop=OP_PUTROOTFH), nfs_argop4(argop=OP_LOOKUP, oplookup=LOOKUP4args(objname='tmp')), nfs_argop4(argop=OP_LOOKUP, oplookup=LOOKUP4args(objname='DELEG15b')), nfs_argop4(argop=OP_SAVEFH), nfs_argop4(argop=OP_PUTROOTFH), nfs_argop4(argop=OP_LOOKUP, oplookup=LOOKUP4args(objname='tmp')), nfs_argop4(argop=OP_LINK, oplink=LINK4args(newname='DELEG15b.link'))])
> COMPOUND4res(status=NFS4ERR_NOENT, tag='', resarray=[nfs_resop4(resop=OP_PUTROOTFH, opputrootfh=PUTROOTFH4res(status=NFS4_OK)), nfs_resop4(resop=OP_LOOKUP, oplookup=LOOKUP4res(status=NFS4_OK)), nfs_resop4(resop=OP_LOOKUP, oplookup=LOOKUP4res(status=NFS4_OK)), nfs_resop4(resop=OP_SAVEFH, opsavefh=SAVEFH4res(status=NFS4_OK)), nfs_resop4(resop=OP_PUTROOTFH, opputrootfh=PUTROOTFH4res(status=NFS4_OK)), nfs_resop4(resop=OP_LOOKUP, oplookup=LOOKUP4res(status=NFS4_OK)), nfs_resop4(resop=OP_LINK, oplink=LINK4res(status=NFS4ERR_NOENT))])
>  *****CB received COMPOUND******
> ******* CB_Recall (id=1)********

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


How reproducible:


Steps to Reproduce:
pynfs/nfs4.0
  
Actual results:


Expected results:


Additional info:

Comment 1 Jian Li 2012-06-03 09:21:46 UTC
This is fixed upstream by 7d751f6f8.

Comment 4 RHEL Program Management 2012-06-04 01:02:21 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 5 yanfu,wang 2012-06-04 03:40:11 UTC
I think it's duplicated with bug 823018, see https://bugzilla.redhat.com/show_bug.cgi?id=823018#c1.

Comment 6 Jian Li 2012-06-04 03:47:42 UTC

*** This bug has been marked as a duplicate of bug 823018 ***


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