From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Fix bug that client use a invaild delegation
Date: Wed, 04 Aug 2010 17:14:45 +0800 [thread overview]
Message-ID: <4C592F85.8070308@cn.fujitsu.com> (raw)
Hi all
I find a bug at RHEL6Beta2. If client return nfsi->delegation, some open_stateid
still have the NFS_DELEGATED_STATE bit, and another open process which has some
owner will not clear this bit, it will not use the new open stateid to fill
state->stateid, just fill state->open_stateid.
Then other IO operation will use the old delegation, it will get NFS4ERR_BAD_STATEID.
Thought my test program just FAIL at RHEL6Beta2, latest kernel is OK,
but i thinks the latest kernel maybe have the some bug.
---
Bian Naimeng (2):
[PATCH 1/2] Make lock inode before lock nfs4_state_owner
[PATCH 2/2] We should clear NFS_DELEGATED_STATE after return delegation
fs/nfs/nfs4proc.c | 15 ++++++++++++++-
fs/nfs/nfs4state.c | 16 +++++++++-------
2 files changed, 23 insertions(+), 8 deletions(-)
--
Regards
Bian Naimeng
next reply other threads:[~2010-08-04 9:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 9:14 Bian Naimeng [this message]
2010-08-04 9:15 ` [PATCH 1/2] Make lock inode before lock nfs4_state_owner Bian Naimeng
2010-08-04 9:18 ` [PATCH 2/2] We should clear NFS_DELEGATED_STATE after return delegation Bian Naimeng
2010-08-04 12:45 ` Trond Myklebust
2010-08-05 2:26 ` Bian Naimeng
2010-08-05 13:03 ` Trond Myklebust
2010-08-06 4:10 ` Bian Naimeng
2010-08-06 13:30 ` Trond Myklebust
2010-08-16 7:50 ` Bian Naimeng
2010-08-17 23:16 ` Trond Myklebust
2010-08-18 3:17 ` Bian Naimeng
2010-08-23 7:43 ` Bian Naimeng
2010-09-01 6:40 ` Bian Naimeng
2010-09-07 22:04 ` Trond Myklebust
2010-09-08 1:33 ` Bian Naimeng
2010-09-08 1:57 ` Trond Myklebust
2010-09-08 2:37 ` Bian Naimeng
2010-09-08 3:11 ` Bian Naimeng
2010-09-08 20:37 ` Trond Myklebust
2010-09-09 1:29 ` Bian Naimeng
2010-11-24 6:27 ` Bian Naimeng
[not found] ` <1283978245.2905.23.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-12-02 8:32 ` Li Yewang
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=4C592F85.8070308@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=Trond.Myklebust@netapp.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).