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 800681 - NFSv4 Fix the handling of a revoked or bad delegation stateid
Summary: NFSv4 Fix the handling of a revoked or bad delegation stateid
Keywords:
Status: CLOSED DUPLICATE of bug 842435
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.3
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: 6.4
Assignee: nfs-maint
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard: NFSv4
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-06 22:58 UTC by Andy Adamson
Modified: 2012-10-12 10:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-12 10:06:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andy Adamson 2012-03-06 22:58:12 UTC
Description of problem:

If we know that the delegation stateid is bad or revoked, we need to
remove that delegation as soon as possible, and then mark all the
stateids that relied on that delegation for recovery. We cannot use
the delegation as part of the recovery process.


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


How reproducible:
100% with the ability for the admin to revoke a stateid on the NFSv4.0/v4.1 server


Steps to Reproduce:
1. Open a file with a delegation
2. Perform I/O - READ the file
3. During I/O revoke the delegation stated
  
Actual results:
A READ will return with NFS4ERR_BAD_STATEID. The client will start the recovery process, but it will not complete.  Either the client will hang, or the READ will be resent with the revoked stateid, and the application will see an input/output error.

Expected results:
With this patch, the (possibly a delegation) stateid is recovered via an OPEN with CLAIM_NULL, the READ is resent with the new stateid and all is well.

Additional info:

Here is the upstream patch queued for stable:

From a1d0b5eebc4fd6e0edb02688b35f17f67f42aea5 Mon Sep 17 00:00:00 2001
From: Trond Myklebust <Trond.Myklebust>
Date: Mon, 5 Mar 2012 19:56:44 -0500
Subject: [PATCH] NFS: Properly handle the case where the delegation is
 revoked

Comment 2 RHEL Program Management 2012-05-03 05:19:13 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Jeff Layton 2012-10-12 10:06:02 UTC

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


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