* Problem with NFSv3 in inode data transfer
@ 2011-01-21 9:07 Giuseppe Gargiuolo
0 siblings, 0 replies; only message in thread
From: Giuseppe Gargiuolo @ 2011-01-21 9:07 UTC (permalink / raw)
To: linux-nfs
We are working on our personal NFS File System version 3 Extension on
Linux Kernel 2.6.34 and we have a problem.
Our problem is:
We want to add four 28-byte-chars to nfs_fattr struct to make my
client read data in the inode from the server for each file/directory
so encoded and decoded them in fs/nfs/nfs3xdr.c making them work.
Our patch works. We worked on functions encode_fattr3(), decode_fattr(),
and in costants:
nfs3_fattr_sz (21+1+(NFS3_MAXTAGLEN>>2)*4) (located in fs/nfs/nfs3xdr.c),
#define NFS3_POST_OP_ATTR_WORDS (22+1+(NFS3_MAXTAGLEN>>2)*4)
(located in include/linux/nfs3.h).
where NFS3_MAXTAGLEN is 28 (max number of chars writable in each field).
When trying to list files in our nfs client directory, kernel returns
ls: reading directory . : Input/Output Error
even if from the dmesg log data seem transfering correctly.
Could be a problem over 20 fields?
We appreciate any help.
Thanks in advance,
Best Regards
Nicola Corriero - Giuseppe Gargiuolo
HiXOS Group
University of Bari
Italy
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-01-21 9:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-21 9:07 Problem with NFSv3 in inode data transfer Giuseppe Gargiuolo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).