Bug 2101371

Summary: nfs listxattr operation NFS4ERR_BAD_COOKIE
Product: [Fedora] Fedora Reporter: radchenkoy
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 35CC: luk.claes, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 18:03:42 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:
Attachments:
Description Flags
tcp dump of nfs listxattr operation. none

Description radchenkoy 2022-06-27 10:16:00 UTC 
Created attachment 1892932 [details]
tcp dump of nfs listxattr operation.

Description of problem:

    https://datatracker.ietf.org/doc/html/rfc8276#section-8.4.3
    "For subsequent LISTXATTRS requests, the client specifies a
    cookie value that is provided by the server on a previous LISTXATTRS
    request."

    I get NFS4ERR_BAD_COOKIE (10003) status code when I use a cookie value that is provided by the server on a previous LISTXATTRS
    request.
    
    See attacment, tcp dump.


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

    Fedora 35

How reproducible:

Steps to Reproduce:
1. Mount nfsv4.2 share
2. request NFS LISTXATTRS operation for the file with many xattr.
3. check result.

Actual results:

1. LISTXATTRS req, cookie=0
2. LISTXATTRS rep, cookie=144115188075855872 (0x200000000000000), list of keys, eof=0

3. LISTXATTRS req, cookie=144115188075855872 (0x200000000000000)
4. LISTXATTRS rep, NFS4ERR_BAD_COOKIE


Expected results:

1. LISTXATTRS req, cookie=0
2. LISTXATTRS rep, cookie=<cookie_num1>, list 1 of keys, eof=0

3. LISTXATTRS req, cookie=<cookie_num1>
4. LISTXATTRS rep, cookie=<cookie_num2>, list 2 of keys, eof=1


Additional info:
Comment 1 Ben Cotton 2022-11-29 18:57:49 UTC 
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 2 Ben Cotton 2022-12-13 18:03:42 UTC 
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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