* [PATCH 1/1] nfs: Panic when commit fails
@ 2009-10-20 17:44 Terry Loftin
2009-10-20 22:06 ` Trond Myklebust
0 siblings, 1 reply; 2+ messages in thread
From: Terry Loftin @ 2009-10-20 17:44 UTC (permalink / raw)
To: SteveD, linux-nfs
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>
---
diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c
index e4e089a..1af78ff 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,
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH 1/1] nfs: Panic when commit fails
2009-10-20 17:44 [PATCH 1/1] nfs: Panic when commit fails Terry Loftin
@ 2009-10-20 22:06 ` Trond Myklebust
0 siblings, 0 replies; 2+ messages in thread
From: Trond Myklebust @ 2009-10-20 22:06 UTC (permalink / raw)
To: Terry Loftin; +Cc: SteveD, linux-nfs
On Tue, 2009-10-20 at 11:44 -0600, Terry Loftin wrote:
> 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>
> ---
>
> diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c
> index e4e089a..1af78ff 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,
Doh! Well spotted. I'll pass this along into mainline+stable.
Cheers
Trond
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-10-20 22:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-20 17:44 [PATCH 1/1] nfs: Panic when commit fails Terry Loftin
2009-10-20 22:06 ` Trond Myklebust
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.