From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs3 implementation issue?
Date: Thu, 17 Nov 2005 00:52:27 -0500 [thread overview]
Message-ID: <1132206747.8029.2.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4ae3c140511162135j7a72299eg8223dfedab8eea62@mail.gmail.com>
On Thu, 2005-11-17 at 00:35 -0500, Xin Zhao wrote:
> 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?
Already fixed. See
http://kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=34123da66e613602de5a886b05c875b6a91b8ed2
Cheers,
Trond
prev parent reply other threads:[~2005-11-17 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 5:35 Xin Zhao
2005-11-17 5:52 ` Trond Myklebust [this message]
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=1132206747.8029.2.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=uszhaoxin@gmail.com \
/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
all inboxes | Powered by JetHome®