From: andros@netapp.com
To: bhalevy@panasas.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/5] cleanup inode.c and bug fixes
Date: Tue, 6 Jul 2010 17:16:57 -0400 [thread overview]
Message-ID: <1278451022-2889-1-git-send-email-andros@netapp.com> (raw)
For the pnfs-submit branch 2.6.35-rc3 7-6-2010 tree.
These first three patches simplify the inode.c pnfs initialization calls.
0001-SQUASHME-pnfs-submit-remove-pnfs_init_once.patch
0002-SQUASHME-pnfs-submit-remove-pnfs_alloc_init_inode.patch
0003-SQUASHME-pnfs-submit-remove-pnfs_destroy_inode.patch
These two patches fix bugs in the layoutget and layoutcommit error handling
where the calldata->status was not set after the async error handler in the
rpc_call_done routines.
0004-SQUASHME-pnfs-submit-set-layoutcommit-status-after-a.patch
0005-SQUASHME-pnfs-submit-set-layoutget-status-after-asyn.patch
Tested:
CONFIG_NFS_V4_1 set:
pNFS mount connectathon tests pass.
pyNFS server with NFS4ERR_DELAY returned by layoutget handles the error in
the async error handler, and then the calldata->status is set to NFS4_OK.
CONFIG_NFS_V4_1 not set;
NFSv4.0 mount passes connectathon tests.
-->Andy
next reply other threads:[~2010-07-06 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 21:16 andros [this message]
2010-07-06 21:16 ` [PATCH 1/5] SQUASHME pnfs-submit: remove pnfs_init_once andros
2010-07-06 21:16 ` [PATCH 2/5] SQUASHME pnfs-submit remove pnfs_alloc_init_inode andros
2010-07-06 21:17 ` [PATCH 3/5] SQUASHME pnfs-submit: remove pnfs_destroy_inode andros
2010-07-06 21:17 ` [PATCH 4/5] SQUASHME pnfs-submit: set layoutcommit status after async error handler andros
2010-07-06 21:17 ` [PATCH 5/5] SQUASHME pnfs-submit: set layoutget " andros
2010-07-07 9:27 ` [PATCH 2/5] SQUASHME pnfs-submit remove pnfs_alloc_init_inode Boaz Harrosh
2010-07-07 17:03 ` William A. (Andy) Adamson
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=1278451022-2889-1-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--cc=bhalevy@panasas.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