From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] Address several issues with TEST_STATEID
Date: Fri, 01 Jun 2012 11:37:57 -0400 [thread overview]
Message-ID: <20120601153231.5626.89559.stgit@degas.1015granger.net> (raw)
Hi-
While testing the recently introduced PURGE_STATE logic, I found some
issues with the error handling logic under nfs41_open_expired().
After fixing these issues, I am able to get Connectathon basic,
general, and special tests to pass with a server rigged to assert
SEQ4_STATUS_ADMIN_STATE_REVOKED at regular intervals. The
Connectathon lock tests encounter a deadlock, which I've already
reported, that appears to pre-date PURGE_STATE.
---
Chuck Lever (4):
NFS: Refactor nfs41_check_expired_stateid()
NFS: state reclaim clears OPEN state
NFS: Properly sort TEST_STATEID results
NFS: Clean up TEST_STATEID and FREE_STATEID proc error reporting
fs/nfs/nfs4proc.c | 144 ++++++++++++++++++++++++++++++++++++++++++-----------
1 files changed, 115 insertions(+), 29 deletions(-)
--
Chuck Lever
next reply other threads:[~2012-06-01 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 15:37 Chuck Lever [this message]
2012-06-01 15:38 ` [PATCH 1/4] NFS: Clean up TEST_STATEID and FREE_STATEID proc error reporting Chuck Lever
2012-06-01 15:38 ` [PATCH 2/4] NFS: Properly sort TEST_STATEID results Chuck Lever
2012-06-01 15:52 ` Chuck Lever
2012-06-01 16:01 ` Myklebust, Trond
2012-06-01 16:19 ` Chuck Lever
2012-06-01 15:39 ` [PATCH 3/4] NFS: state reclaim clears OPEN state Chuck Lever
2012-06-01 15:39 ` [PATCH 4/4] NFS: Refactor nfs41_check_expired_stateid() Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120601153231.5626.89559.stgit@degas.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).