DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=FPgtzguL+8OX/grG3tqgLX+089oNRBzqtyXu8SuwhOL0QHIDmpY7XNnJUflT4rWTEzAo4mWmwLIKqh4I+FKlz3Wki7o5TPKgIwLiZvpazbWQT30eJSztSRdDfKBln8ukHpRy6Ub98GInXoxsAjV7Y7ojdbNBtLQmQyBpd3e6sj8=
Message-ID: <4ae3c140511162135j7a72299eg8223dfedab8eea62@mail.gmail.com>
Date: Thu, 17 Nov 2005 00:35:43 -0500
From: Xin Zhao <uszhaoxin@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: nfs3 implementation issue?
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 676
Lines: 19

In nfs/nfs3proc.c: nfs3_read_done(), I saw the following line:

   struct nfs_write_data *data = (struct nfs_write_data *) task->tk_calldata;

I don't know why the tk_calldata is regarded as nfs_write_data instead
of nfs_read_data. When this rpc call is set up, we put
task->tk_calldata as a nfs_read_data object, why will it become a
nfs_write_data after the rpc call is done?

Can someone explain this a little bit?

Thanks!

Xin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/