Commit 3fe433a
committed
NFSv4: Retry LOCK on OLD_STATEID during delegation return
jira LE-1907
Rebuild_History Non-Buildable kernel-rt-5.14.0-284.30.1.rt14.315.el9_2
commit-author Benjamin Coddington <bcodding@redhat.com>
commit f5ea161
There's a small window where a LOCK sent during a delegation return can
race with another OPEN on client, but the open stateid has not yet been
updated. In this case, the client doesn't handle the OLD_STATEID error
from the server and will lose this lock, emitting:
"NFS: nfs4_handle_delegation_recall_error: unhandled error -10024".
Fix this by sending the task through the nfs4 error handling in
nfs4_lock_done() when we may have to reconcile our stateid with what the
server believes it to be. For this case, the result is a retry of the
LOCK operation with the updated stateid.
Reported-by: Gonzalo Siero Humet <gsierohu@redhat.com>
Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
(cherry picked from commit f5ea161)
Signed-off-by: Jonathan Maple <jmaple@ciq.com>1 parent 6831af1 commit 3fe433a
1 file changed
+4
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7108 | 7108 | | |
7109 | 7109 | | |
7110 | 7110 | | |
| 7111 | + | |
7111 | 7112 | | |
7112 | 7113 | | |
7113 | 7114 | | |
7114 | 7115 | | |
7115 | 7116 | | |
7116 | 7117 | | |
7117 | 7118 | | |
7118 | | - | |
7119 | | - | |
| 7119 | + | |
7120 | 7120 | | |
7121 | 7121 | | |
7122 | 7122 | | |
| |||
7137 | 7137 | | |
7138 | 7138 | | |
7139 | 7139 | | |
| 7140 | + | |
| 7141 | + | |
7140 | 7142 | | |
7141 | 7143 | | |
7142 | 7144 | | |
| |||
0 commit comments