tree 8a91dcd2149f47d2a2b6f7b49d653dd168c908a8
parent 964fe080d94db82a3268443e9b9ece4c60246414
author Terry Loftin <terry.loftin@hp.com> 1256261761 -0400
committer Trond Myklebust <Trond.Myklebust@netapp.com> 1256321790 -0400

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>