aboutsummaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorTerry Loftin <terry.loftin@hp.com>2009-10-22 21:36:01 -0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2009-10-23 14:16:30 -0400
commita8b40bc7e635831b61c43acc71a86d3a68b2dff0 (patch)
tree8a91dcd2149f47d2a2b6f7b49d653dd168c908a8 /fs
parent964fe080d94db82a3268443e9b9ece4c60246414 (diff)
downloadkernel_samsung_smdk4412-a8b40bc7e635831b61c43acc71a86d3a68b2dff0.zip
kernel_samsung_smdk4412-a8b40bc7e635831b61c43acc71a86d3a68b2dff0.tar.gz
kernel_samsung_smdk4412-a8b40bc7e635831b61c43acc71a86d3a68b2dff0.tar.bz2
nfs: Panic when commit fails
Actually pass the NFS_FILE_SYNC option to the server to avoid a Panic in nfs_direct_write_complete() when a commit fails. At the end of an nfs write, if the nfs commit fails, all the writes will be rescheduled. They are supposed to be rescheduled as NFS_FILE_SYNC writes, but the rpc_task structure is not completely intialized and so the option is not passed. When the rescheduled writes complete, the return indicates that they are NFS_UNSTABLE and we try to do another commit. This leads to a Panic because the commit data structure pointer was set to null in the initial (failed) commit attempt. Signed-off-by: Terry Loftin <terry.loftin@hp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs')
-rw-r--r--fs/nfs/direct.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c
index 6c32100..e1d415e 100644
--- a/fs/nfs/direct.c
+++ b/fs/nfs/direct.c
@@ -457,6 +457,7 @@ static void nfs_direct_write_reschedule(struct nfs_direct_req *dreq)
};
struct rpc_task_setup task_setup_data = {
.rpc_client = NFS_CLIENT(inode),
+ .rpc_message = &msg,
.callback_ops = &nfs_write_direct_ops,
.workqueue = nfsiod_workqueue,
.flags = RPC_TASK_ASYNC,