From: Tom Tucker <tom@opengridcomputing.com>
To: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: [PATCH] PNFS: filelayout_commit corrupts RPC all_tasks
Date: Wed, 05 Sep 2007 13:03:18 -0500 [thread overview]
Message-ID: <1189015398.22424.54.camel@trinity.ogc.int> (raw)
The filelayout_commit function incorrectly releases the nfs_write_data
pointed to by 'data'. Basically, the task contained in the nfs_write_data
structure has already been initialized (rpc_init_task) up in the generic NFS
commit logic. Calling nfs4_commit_free frees the memory, but doesn't remove
the task from the RPC all_tasks list. With debug turned on, the task list
is corrupted immediately by poison_obj; without debug, a freed task is
sitting on the all_tasks list and will eventually be corrupted when the
memory is reused.
Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
---
fs/nfs/nfs4filelayout.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/nfs/nfs4filelayout.c b/fs/nfs/nfs4filelayout.c
index 86ced63..1a32925 100644
--- a/fs/nfs/nfs4filelayout.c
+++ b/fs/nfs/nfs4filelayout.c
@@ -583,7 +583,7 @@ filelayout_commit(struct pnfs_layout_typ
}
/* Release original commit data since it is not used */
- nfs4_commit_free(data);
+ rpc_release_task(&data->task);
return 0;
out_bad:
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-09-05 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 18:03 Tom Tucker [this message]
2007-09-05 18:17 ` [PATCH] PNFS: filelayout_commit corrupts RPC all_tasks J. Bruce Fields
2007-09-05 18:43 ` Tom Tucker
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=1189015398.22424.54.camel@trinity.ogc.int \
--to=tom@opengridcomputing.com \
--cc=nfs@lists.sourceforge.net \
/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