virtio-9p: getattr server implementation for 9P2000.L protocol.
PATCH 1/1 virtio-9p: getattr server implementation for 9P2000.L protocol.
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.
qid.vers[4]
version number for given path
qid.path[8]
the file server's unique identification for the file
st_mode[4]
Permission and flags
st_nlink[8]
Number of hard links
st_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_rdev[8]
Device ID (if special file)
st_size[8]
Size, in bytes
st_blksize[8]
Block size for file system IO
st_blocks[8]
Number of file system blocks allocated
st_atime_sec[8]
Time of last access, seconds
st_atime_nsec[8]
Time of last access, nanoseconds
st_mtime_sec[8]
Time of last modification, seconds
st_mtime_nsec[8]
Time of last modification, nanoseconds
st_ctime_sec[8]
Time of last status change, seconds
st_ctime_nsec[8]
Time of last status change, nanoseconds
This patch implements the client side of getattr implementation for 9P2000.L. It introduces a new structure p9_stat_dotl for getting Linux stat information along with QID. The data layout is similar to stat structure in Linux user space with the following major differences:
inode (st_ino) is not part of data. Instead qid is.
device (st_dev) is not part of data because this doesn't make sense on the client.
All time variables are 64 bit wide on the wire. The kernel seems to use 32 bit variables for these variables. However, some of the architectures have used 64 bit variables and glibc exposes 64 bit variables to user space on some architectures. Hence to be on the safer side we have made these 64 bit in the protocol. Refer to the comments in include/asm-generic/stat.h
---
hw/virtio-9p-debug.c | 32 ++++++++++++++++++++ hw/virtio-9p.c | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++ hw/virtio-9p.h | 28 +++++++++++++++++ 3 files changed, 142 insertions(+), 0 deletions(-)
hw/virtio-9p-debug.c +32 -0
@@ -178,6 +178,30 @@ static void pprint_stat(V9fsPDU *pdu, int rx, size_t *offsetp, const char *name)fprintf (llogfile,"}" ); } +static void pprint_stat_dotl (V9fsPDU *pdu,int rx,size_t *offsetp, +const char *name) +{ +fprintf (llogfile,"%s={" , name); +pprint_qid (pdu, rx, offsetp,"qid" ); +pprint_int32 (pdu, rx, offsetp,", st_mode" ); +pprint_int64 (pdu, rx, offsetp,", st_nlink" ); +pprint_int32 (pdu, rx, offsetp,", st_uid" ); +pprint_int32 (pdu, rx, offsetp,", st_gid" ); +pprint_int64 (pdu, rx, offsetp,", st_rdev" ); +pprint_int64 (pdu, rx, offsetp,", st_size" ); +pprint_int64 (pdu, rx, offsetp,", st_blksize" ); +pprint_int64 (pdu, rx, offsetp,", st_blocks" ); +pprint_int64 (pdu, rx, offsetp,", atime" ); +pprint_int64 (pdu, rx, offsetp,", atime_nsec" ); +pprint_int64 (pdu, rx, offsetp,", mtime" ); +pprint_int64 (pdu, rx, offsetp,", mtime_nsec" ); +pprint_int64 (pdu, rx, offsetp,", ctime" ); +pprint_int64 (pdu, rx, offsetp,", ctime_nsec" ); +fprintf (llogfile,"}" ); +} + + +static void pprint_strs (V9fsPDU *pdu,int rx,size_t *offsetp,const char *name) {int sg_count =get_sg_count (pdu, rx);
@@ -351,6 +375,14 @@ void pprint_pdu(V9fsPDU *pdu)pprint_int32 (pdu,1 , &offset,"msize" );pprint_str (pdu,1 , &offset,", version" );break ; +case P9_TGETATTR : +fprintf (llogfile,"TGETATTR: (" ); +pprint_int32 (pdu,0 , &offset,"fid" ); +break ; +case P9_RGETATTR : +fprintf (llogfile,"RGETATTR: (" ); +pprint_stat_dotl (pdu,1 , &offset,"getattr" ); +break ;case P9_TAUTH :fprintf (llogfile,"TAUTH: (" );pprint_int32 (pdu,0 , &offset,"afid" );
hw/virtio-9p.c +82 -0
106 lines not on this page · raw message
hw/virtio-9p.h +28 -0
@@ -15,6 +15,8 @@enum {P9_TSTATFS =8 ,P9_RSTATFS , +P9_TGETATTR =24 , +P9_RGETATTR ,P9_TREADDIR =40 ,P9_RREADDIR ,P9_TVERSION =100 ,
@@ -177,6 +179,32 @@ typedef struct V9fsStatState {struct stat stbuf; } V9fsStatState; +typedef struct V9fsStatDotl { +V9fsQID qid; +uint32_t st_mode; +uint64_t st_nlink; +uint32_t st_uid; +uint32_t st_gid; +uint64_t st_rdev; +uint64_t st_size; +uint64_t st_blksize; +uint64_t st_blocks; +uint64_t st_atime_sec; +uint64_t st_atime_nsec; +uint64_t st_mtime_sec; +uint64_t st_mtime_nsec; +uint64_t st_ctime_sec; +uint64_t st_ctime_nsec; +}V9fsStatDotl ; + +typedef struct V9fsStatStateDotl { +V9fsPDU *pdu; +size_t offset; +V9fsStatDotl v9stat_dotl; +struct stat stbuf; +}V9fsStatStateDotl ; + + typedef struct V9fsWalkState { V9fsPDU *pdu; size_t offset;
Quoted 37 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of owner
Quoted 8 lines
st_rdev[8]
Device ID (if special file)st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IO
So it should be scaled by iounit right ? If we say 9p block size is iounit.
Quoted 3 lines
st_blocks[8]
Number of file system blocks allocated
same here.
Quoted 248 lines
st_atime_sec[8]
Time of last access, secondsst_atime_nsec[8]
Time of last access, nanosecondsst_mtime_sec[8]
Time of last modification, secondsst_mtime_nsec[8]
Time of last modification, nanosecondsst_ctime_sec[8]
Time of last status change, secondsst_ctime_nsec[8]
Time of last status change, nanosecondsThis patch implements the client side of getattr implementation for 9P2000.L. It introduces a new structure
p9_stat_dotlfor getting Linux stat information along with QID. The data layout is similar to stat structure in Linux user space with the following major differences:inode (
st_ino) is not part of data. Instead qid is.device (
st_dev) is not part of data because this doesn't make sense on the client.All time variables are 64 bit wide on the wire. The kernel seems to use 32 bit variables for these variables. However, some of the architectures have used 64 bit variables and glibc exposes 64 bit variables to user space on some architectures. Hence to be on the safer side we have made these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.hSigned-off-by M. Mohan Kumar <[email protected]>Signed-off-by Sripathi Kodi <[email protected]>---
hw/virtio-9p-debug.c | 32 ++++++++++++++++++++ hw/virtio-9p.c | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++ hw/virtio-9p.h | 28 +++++++++++++++++ 3 files changed, 142 insertions(+), 0 deletions(-)hw/virtio-9p-debug.c +32
-0@@ -178,6 +178,30 @@ static void pprint_stat(V9fsPDU *pdu, int rx, size_t *offsetp, const char *name)fprintf (llogfile,"}" ); } +static void pprint_stat_dotl (V9fsPDU *pdu,int rx,size_t *offsetp, +const char *name) +{ +fprintf (llogfile,"%s={" , name); +pprint_qid (pdu, rx, offsetp,"qid" ); +pprint_int32 (pdu, rx, offsetp,", st_mode" ); +pprint_int64 (pdu, rx, offsetp,", st_nlink" ); +pprint_int32 (pdu, rx, offsetp,", st_uid" ); +pprint_int32 (pdu, rx, offsetp,", st_gid" ); +pprint_int64 (pdu, rx, offsetp,", st_rdev" ); +pprint_int64 (pdu, rx, offsetp,", st_size" ); +pprint_int64 (pdu, rx, offsetp,", st_blksize" ); +pprint_int64 (pdu, rx, offsetp,", st_blocks" ); +pprint_int64 (pdu, rx, offsetp,", atime" ); +pprint_int64 (pdu, rx, offsetp,", atime_nsec" ); +pprint_int64 (pdu, rx, offsetp,", mtime" ); +pprint_int64 (pdu, rx, offsetp,", mtime_nsec" ); +pprint_int64 (pdu, rx, offsetp,", ctime" ); +pprint_int64 (pdu, rx, offsetp,", ctime_nsec" ); +fprintf (llogfile,"}" ); +} + + +static void pprint_strs (V9fsPDU *pdu,int rx,size_t *offsetp,const char *name) {int sg_count =get_sg_count (pdu, rx);@@ -351,6 +375,14 @@ void pprint_pdu(V9fsPDU *pdu)pprint_int32 (pdu,1 , &offset,"msize" );pprint_str (pdu,1 , &offset,", version" );break ; +case P9_TGETATTR : +fprintf (llogfile,"TGETATTR: (" ); +pprint_int32 (pdu,0 , &offset,"fid" ); +break ; +case P9_RGETATTR : +fprintf (llogfile,"RGETATTR: (" ); +pprint_stat_dotl (pdu,1 , &offset,"getattr" ); +break ;case P9_TAUTH :fprintf (llogfile,"TAUTH: (" );pprint_int32 (pdu,0 , &offset,"afid" );hw/virtio-9p.c +82
-0@@ -737,6 +737,17 @@ static size_t pdu_marshal(V9fsPDU *pdu, size_t offset, const char *fmt, ...) statp->n_gid, statp->n_muid);break ; } +case 'A' : { + V9fsStatDotl *statp = va_arg(ap, V9fsStatDotl *); + offset +=pdu_marshal (pdu, offset,"Qdqddqqqqqqqqqq" , + &statp->qid, statp->st_mode, statp->st_nlink, + statp->st_uid, statp->st_gid, statp->st_rdev, + statp->st_size, statp->st_blksize, statp->st_blocks, + statp->st_atime_sec, statp->st_atime_nsec, + statp->st_mtime_sec, statp->st_mtime_nsec, + statp->st_ctime_sec, statp->st_ctime_nsec); +break ; + }default :break ; }@@ -964,6 +975,29 @@ static int stat_to_v9stat(V9fsState *s, V9fsString *name,return 0 ; } +static void stat_to_v9stat_dotl (V9fsState *s,const struct stat *stbuf, +V9fsStatDotl *v9lstat) +{ +memset (v9lstat,0 ,sizeof (*v9lstat)); + + v9lstat->st_mode = stbuf->st_mode; + v9lstat->st_nlink = stbuf->st_nlink; + v9lstat->st_uid = stbuf->st_uid; + v9lstat->st_gid = stbuf->st_gid; + v9lstat->st_rdev = stbuf->st_rdev; + v9lstat->st_size = stbuf->st_size; + v9lstat->st_blksize = stbuf->st_blksize; + v9lstat->st_blocks = stbuf->st_blocks; + v9lstat->st_atime_sec = stbuf->st_atime; + v9lstat->st_atime_nsec = stbuf->st_atim.tv_nsec; + v9lstat->st_mtime_sec = stbuf->st_mtime; + v9lstat->st_mtime_nsec = stbuf->st_mtim.tv_nsec; + v9lstat->st_ctime_sec = stbuf->st_ctime; + v9lstat->st_ctime_nsec = stbuf->st_ctim.tv_nsec; + +stat_to_qid (stbuf, &v9lstat->qid); +} +static struct iovec *adjust_sg (struct iovec *sg,int len,int *iovcnt) {while (len && *iovcnt) {@@ -1131,6 +1165,53 @@ out:qemu_free (vs); } +static void v9fs_getattr_post_lstat (V9fsState *s,V9fsStatStateDotl *vs, +int err) +{ +if (err ==-1 ) { + err = -errno; + goto out; + } + +stat_to_v9stat_dotl (s, &vs->stbuf, &vs->v9stat_dotl); + vs->offset +=pdu_marshal (vs->pdu, vs->offset,"A" , &vs->v9stat_dotl); + err = vs->offset; + +out: +complete_pdu (s, vs->pdu, err); +qemu_free (vs); +} + +static void v9fs_getattr (V9fsState *s,V9fsPDU *pdu) +{ +int32_t fid; +V9fsStatStateDotl *vs; +ssize_t err =0 ; +V9fsFidState *fidp; + + vs =qemu_malloc (sizeof (*vs)); + vs->pdu = pdu; + vs->offset =7 ; + +memset (&vs->v9stat_dotl,0 ,sizeof (vs->v9stat_dotl)); + +pdu_unmarshal (vs->pdu, vs->offset,"d" , &fid); + + fidp =lookup_fid (s, fid); +if (fidp ==NULL ) { + err = -ENOENT ; + goto out; + } + + err =v9fs_do_lstat (s, &fidp->path, &vs->stbuf); +v9fs_getattr_post_lstat (s, vs, err); +return ; + +out: +complete_pdu (s, vs->pdu, err); +qemu_free (vs); +} +static void v9fs_walk_complete (V9fsState *s,V9fsWalkState *vs,int err) {complete_pdu (s, vs->pdu, err);@@ -2343,6 +2424,7 @@ typedef void (pdu_handler_t)(V9fsState *s, V9fsPDU *pdu);static pdu_handler_t *pdu_handlers[] = { [P9_TREADDIR ] = v9fs_readdir, [P9_TSTATFS ] = v9fs_statfs, + [P9_TGETATTR ] = v9fs_getattr, [P9_TVERSION ] = v9fs_version, [P9_TATTACH ] = v9fs_attach, [P9_TSTAT ] = v9fs_stat,hw/virtio-9p.h +21
-0@@ -15,6 +15,8 @@enum {P9_TSTATFS =8 ,P9_RSTATFS , +P9_TGETATTR =24 , +P9_RGETATTR ,P9_TREADDIR =40 ,P9_RREADDIR ,P9_TVERSION =100 ,@@ -177,6 +179,32 @@ typedef struct V9fsStatState {struct stat stbuf; } V9fsStatState; +typedef struct V9fsStatDotl { +V9fsQID qid; +uint32_t st_mode; +uint64_t st_nlink; +uint32_t st_uid; +uint32_t st_gid; +uint64_t st_rdev; +uint64_t st_size; +uint64_t st_blksize; +uint64_t st_blocks; +uint64_t st_atime_sec; +uint64_t st_atime_nsec; +uint64_t st_mtime_sec; +uint64_t st_mtime_nsec; +uint64_t st_ctime_sec; +uint64_t st_ctime_nsec; +}V9fsStatDotl ; + +typedef struct V9fsStatStateDotl {
hw/virtio-9p.h typedef struct V9fsStatState { · line 210
Quoted 10 lines
hw/virtio-9p.h +7
-0+V9fsPDU *pdu; +size_t offset; +V9fsStatDotl v9stat_dotl; +struct stat stbuf; +} V9fsStatStateDotl; + + typedef struct V9fsWalkState { V9fsPDU *pdu; size_t offset;
-aneesh
Quoted 41 lines · On Wed, 02 Jun 2010 19:49:24 +0530 "Aneesh Kumar K. V"…
Quoted 40 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)
Quoted 8 lines
Quoted 5 lines
st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOSo it should be scaled by iounit right ? If we say 9p block size is iounit.
Yes, I think it should be iounit. Currently st_blksize being returned in stat structure to the user space does not use this field that comes from the server. It is being calculated as follows in generic_fillattr():
stat->blksize = (1 << inode->i_blkbits);
So there may not be a need to put st_blksize on the protocol. Further, inode->i_blkbits is copied from sb->s_blocksize_bits. For 9P this value is obtained as:
sb->s_blocksize_bits = fls(v9ses->maxdata - 1);
andv9ses->maxdata = v9ses->clnt->msize - P9_IOHDRSZ;
Due to the above calculation sometimes stat() on a file can report incorrect values. For example, if I mount 9P file system with msize=5000 stat on a file shows me IO Block: 8192! However, we don't consider this when we do actual file data transfer. We use clnt->msize - P9_IOHDRSZ.
Hence it looks to me like i_blkbits is only used to return stat data.
Quoted 7 lines
Quoted 5 lines
st_blocks[8]
Number of file system blocks allocatedsame here.
Yes, this should be file size/iounit.
Thanks,
Sripathi.
Quoted 262 lines
Quoted 249 lines
st_atime_sec[8]
Time of last access, secondsst_atime_nsec[8]
Time of last access, nanosecondsst_mtime_sec[8]
Time of last modification, secondsst_mtime_nsec[8]
Time of last modification, nanosecondsst_ctime_sec[8]
Time of last status change, secondsst_ctime_nsec[8]
Time of last status change, nanosecondsThis patch implements the client side of getattr implementation for 9P2000.L. It introduces a new structure
p9_stat_dotlfor getting Linux stat information along with QID. The data layout is similar to stat structure in Linux user space with the following major differences:inode (
st_ino) is not part of data. Instead qid is.device (
st_dev) is not part of data because this doesn't make sense on the client.All time variables are 64 bit wide on the wire. The kernel seems to use 32 bit variables for these variables. However, some of the architectures have used 64 bit variables and glibc exposes 64 bit variables to user space on some architectures. Hence to be on the safer side we have made these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.hSigned-off-by M. Mohan Kumar <[email protected]>Signed-off-by Sripathi Kodi <[email protected]>---
hw/virtio-9p-debug.c | 32 ++++++++++++++++++++ hw/virtio-9p.c | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++ hw/virtio-9p.h | 28 +++++++++++++++++ 3 files changed, 142 insertions(+), 0 deletions(-)hw/virtio-9p-debug.c +32
-0@@ -178,6 +178,30 @@ static void pprint_stat(V9fsPDU *pdu, int rx, size_t *offsetp, const char *name)fprintf (llogfile,"}" ); } +static void pprint_stat_dotl (V9fsPDU *pdu,int rx,size_t *offsetp, +const char *name) +{ +fprintf (llogfile,"%s={" , name); +pprint_qid (pdu, rx, offsetp,"qid" ); +pprint_int32 (pdu, rx, offsetp,", st_mode" ); +pprint_int64 (pdu, rx, offsetp,", st_nlink" ); +pprint_int32 (pdu, rx, offsetp,", st_uid" ); +pprint_int32 (pdu, rx, offsetp,", st_gid" ); +pprint_int64 (pdu, rx, offsetp,", st_rdev" ); +pprint_int64 (pdu, rx, offsetp,", st_size" ); +pprint_int64 (pdu, rx, offsetp,", st_blksize" ); +pprint_int64 (pdu, rx, offsetp,", st_blocks" ); +pprint_int64 (pdu, rx, offsetp,", atime" ); +pprint_int64 (pdu, rx, offsetp,", atime_nsec" ); +pprint_int64 (pdu, rx, offsetp,", mtime" ); +pprint_int64 (pdu, rx, offsetp,", mtime_nsec" ); +pprint_int64 (pdu, rx, offsetp,", ctime" ); +pprint_int64 (pdu, rx, offsetp,", ctime_nsec" ); +fprintf (llogfile,"}" ); +} + + +static void pprint_strs (V9fsPDU *pdu,int rx,size_t *offsetp,const char *name) {int sg_count =get_sg_count (pdu, rx);@@ -351,6 +375,14 @@ void pprint_pdu(V9fsPDU *pdu)pprint_int32 (pdu,1 , &offset,"msize" );pprint_str (pdu,1 , &offset,", version" );break ; +case P9_TGETATTR : +fprintf (llogfile,"TGETATTR: (" ); +pprint_int32 (pdu,0 , &offset,"fid" ); +break ; +case P9_RGETATTR : +fprintf (llogfile,"RGETATTR: (" ); +pprint_stat_dotl (pdu,1 , &offset,"getattr" ); +break ;case P9_TAUTH :fprintf (llogfile,"TAUTH: (" );pprint_int32 (pdu,0 , &offset,"afid" );hw/virtio-9p.c +82
-0@@ -737,6 +737,17 @@ static size_t pdu_marshal(V9fsPDU *pdu, size_t offset, const char *fmt, ...) statp->n_gid, statp->n_muid);break ; } +case 'A' : { + V9fsStatDotl *statp = va_arg(ap, V9fsStatDotl *); + offset +=pdu_marshal (pdu, offset,"Qdqddqqqqqqqqqq" , + &statp->qid, statp->st_mode, statp->st_nlink, + statp->st_uid, statp->st_gid, statp->st_rdev, + statp->st_size, statp->st_blksize, statp->st_blocks, + statp->st_atime_sec, statp->st_atime_nsec, + statp->st_mtime_sec, statp->st_mtime_nsec, + statp->st_ctime_sec, statp->st_ctime_nsec); +break ; + }default :break ; }@@ -964,6 +975,29 @@ static int stat_to_v9stat(V9fsState *s, V9fsString *name,return 0 ; } +static void stat_to_v9stat_dotl (V9fsState *s,const struct stat *stbuf, +V9fsStatDotl *v9lstat) +{ +memset (v9lstat,0 ,sizeof (*v9lstat)); + + v9lstat->st_mode = stbuf->st_mode; + v9lstat->st_nlink = stbuf->st_nlink; + v9lstat->st_uid = stbuf->st_uid; + v9lstat->st_gid = stbuf->st_gid; + v9lstat->st_rdev = stbuf->st_rdev; + v9lstat->st_size = stbuf->st_size; + v9lstat->st_blksize = stbuf->st_blksize; + v9lstat->st_blocks = stbuf->st_blocks; + v9lstat->st_atime_sec = stbuf->st_atime; + v9lstat->st_atime_nsec = stbuf->st_atim.tv_nsec; + v9lstat->st_mtime_sec = stbuf->st_mtime; + v9lstat->st_mtime_nsec = stbuf->st_mtim.tv_nsec; + v9lstat->st_ctime_sec = stbuf->st_ctime; + v9lstat->st_ctime_nsec = stbuf->st_ctim.tv_nsec; + +stat_to_qid (stbuf, &v9lstat->qid); +} +static struct iovec *adjust_sg (struct iovec *sg,int len,int *iovcnt) {while (len && *iovcnt) {@@ -1131,6 +1165,53 @@ out:qemu_free (vs); } +static void v9fs_getattr_post_lstat (V9fsState *s,V9fsStatStateDotl *vs, +int err) +{ +if (err ==-1 ) { + err = -errno; + goto out; + } + +stat_to_v9stat_dotl (s, &vs->stbuf, &vs->v9stat_dotl); + vs->offset +=pdu_marshal (vs->pdu, vs->offset,"A" , &vs->v9stat_dotl); + err = vs->offset; + +out: +complete_pdu (s, vs->pdu, err); +qemu_free (vs); +} + +static void v9fs_getattr (V9fsState *s,V9fsPDU *pdu) +{ +int32_t fid; +V9fsStatStateDotl *vs; +ssize_t err =0 ; +V9fsFidState *fidp; + + vs =qemu_malloc (sizeof (*vs)); + vs->pdu = pdu; + vs->offset =7 ; + +memset (&vs->v9stat_dotl,0 ,sizeof (vs->v9stat_dotl)); + +pdu_unmarshal (vs->pdu, vs->offset,"d" , &fid); + + fidp =lookup_fid (s, fid); +if (fidp ==NULL ) { + err = -ENOENT ; + goto out; + } + + err =v9fs_do_lstat (s, &fidp->path, &vs->stbuf); +v9fs_getattr_post_lstat (s, vs, err); +return ; + +out: +complete_pdu (s, vs->pdu, err); +qemu_free (vs); +} +static void v9fs_walk_complete (V9fsState *s,V9fsWalkState *vs,int err) {complete_pdu (s, vs->pdu, err);@@ -2343,6 +2424,7 @@ typedef void (pdu_handler_t)(V9fsState *s, V9fsPDU *pdu);static pdu_handler_t *pdu_handlers[] = { [P9_TREADDIR ] = v9fs_readdir, [P9_TSTATFS ] = v9fs_statfs, + [P9_TGETATTR ] = v9fs_getattr, [P9_TVERSION ] = v9fs_version, [P9_TATTACH ] = v9fs_attach, [P9_TSTAT ] = v9fs_stat,hw/virtio-9p.h +21
-0@@ -15,6 +15,8 @@enum {P9_TSTATFS =8 ,P9_RSTATFS , +P9_TGETATTR =24 , +P9_RGETATTR ,P9_TREADDIR =40 ,P9_RREADDIR ,P9_TVERSION =100 ,@@ -177,6 +179,32 @@ typedef struct V9fsStatState {struct stat stbuf; } V9fsStatState; +typedef struct V9fsStatDotl { +V9fsQID qid; +uint32_t st_mode; +uint64_t st_nlink; +uint32_t st_uid; +uint32_t st_gid; +uint64_t st_rdev; +uint64_t st_size; +uint64_t st_blksize; +uint64_t st_blocks; +uint64_t st_atime_sec; +uint64_t st_atime_nsec; +uint64_t st_mtime_sec; +uint64_t st_mtime_nsec; +uint64_t st_ctime_sec; +uint64_t st_ctime_nsec; +}V9fsStatDotl ; + +typedef struct V9fsStatStateDotl {hw/virtio-9p.h typedef struct V9fsStatState { · line 210
Quoted 10 lines
hw/virtio-9p.h +7
-0+V9fsPDU *pdu; +size_t offset; +V9fsStatDotl v9stat_dotl; +struct stat stbuf; +} V9fsStatStateDotl; + + typedef struct V9fsWalkState { V9fsPDU *pdu; size_t offset;-aneesh
Quoted 58 lines · Sripathi Kodi
Quoted 41 lines · On Wed, 02 Jun 2010 19:49:24 +0530 "Aneesh Kumar K. V"…
Quoted 40 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)Quoted 8 lines
Quoted 5 lines
st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOSo it should be scaled by iounit right ? If we say 9p block size is iounit.
Yes, I think it should be iounit. Currently
st_blksizebeing returned in stat structure to the user space does not use this field that comes from the server. It is being calculated as follows ingeneric_fillattr():
Quoted 5 lines
stat->blksize = (1 << inode->i_blkbits);So there may not be a need to put
st_blksizeon the protocol. Further,inode->i_blkbitsis copied fromsb->s_blocksize_bits. For 9P this value is obtained as:
That is what linux kernel currently does. But from the protocol point of view and not looking at specific linux implementation i would suggest to put st_blksize on wire.
-aneesh
Quoted 59 lines · Aneesh Kumar K. V
Quoted 58 lines · Sripathi Kodi
Quoted 41 lines · On Wed, 02 Jun 2010 19:49:24 +0530 "Aneesh Kumar K. V"…
Quoted 40 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)Quoted 7 lines
Quoted 5 lines
st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOSo it should be scaled by iounit right ? If we say 9p block size is iounit.
Yes, I think it should be iounit. Currently
st_blksizebeing returned in stat structure to the user space does not use this field that comes from the server. It is being calculated as follows ingeneric_fillattr():stat->blksize = (1 << inode->i_blkbits);
Quoted 7 lines
Quoted 3 lines
So there may not be a need to put
st_blksizeon the protocol. Further,inode->i_blkbitsis copied fromsb->s_blocksize_bits. For 9P this value is obtained as:That is what linux kernel currently does. But from the protocol point of view and not looking at specific linux implementation i would suggest to put
st_blksizeon wire.
This is part of .L protocol. Specifically for Linux systems. So, if Linux is already doing it, I don't think we need to repeat it.
Thanks,
JV
Quoted 4 lines
-aneesh
Quoted 64 lines · Venkateswararao Jujjuri (JV)
Quoted 63 lines · Aneesh Kumar K. V
Quoted 61 lines · Sripathi Kodi
Quoted 41 lines · On Wed, 02 Jun 2010 19:49:24 +0530 "Aneesh Kumar K. V"…
Quoted 40 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)Quoted 7 lines
Quoted 5 lines
st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOSo it should be scaled by iounit right ? If we say 9p block size is iounit.
Yes, I think it should be iounit. Currently
st_blksizebeing returned in stat structure to the user space does not use this field that comes from the server. It is being calculated as follows ingeneric_fillattr():stat->blksize = (1 << inode->i_blkbits);So there may not be a need to put
st_blksizeon the protocol. Further,inode->i_blkbitsis copied fromsb->s_blocksize_bits. For 9P this value is obtained as:
Quoted 7 lines
Quoted 3 lines
That is what linux kernel currently does. But from the protocol point of view and not looking at specific linux implementation i would suggest to put
st_blksizeon wire.This is part of .L protocol. Specifically for Linux systems. So, if Linux is already doing it, I don't think we need to repeat it.
But nothing prevents from changing Linux internal implementation. So we can't depend on Linux kernel internal implementation. Later in 2.6.x we may not derive stat->blksize from inode->i_blkbits at all. So we cannot depend on Linux kernel internal implementation.
-aneesh
Quoted 69 lines · On Sat, 05 Jun 2010 19:11:53 +0530 "Aneesh Kumar K. V"…
Quoted 68 lines · Venkateswararao Jujjuri (JV)
Quoted 66 lines · Aneesh Kumar K. V
Quoted 56 lines · Sripathi Kodi
Quoted 41 lines · On Wed, 02 Jun 2010 19:49:24 +0530 "Aneesh Kumar K. V"…
Quoted 40 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)Quoted 7 lines
Quoted 5 lines
st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOSo it should be scaled by iounit right ? If we say 9p block size is iounit.
Yes, I think it should be iounit. Currently
st_blksizebeing returned in stat structure to the user space does not use this field that comes from the server. It is being calculated as follows ingeneric_fillattr():Quoted 5 lines
stat->blksize = (1 << inode->i_blkbits);So there may not be a need to put
st_blksizeon the protocol. Further,inode->i_blkbitsis copied fromsb->s_blocksize_bits. For 9P this value is obtained as:That is what linux kernel currently does. But from the protocol point of view and not looking at specific linux implementation i would suggest to put
st_blksizeon wire.
Quoted 8 lines
Quoted 3 lines
This is part of .L protocol. Specifically for Linux systems. So, if Linux is already doing it, I don't think we need to repeat it.
But nothing prevents from changing Linux internal implementation. So we can't depend on Linux kernel internal implementation. Later in 2.6.x we may not derive
stat->blksizefrominode->i_blkbitsat all. So we cannot depend on Linux kernel internal implementation.
Okay, agreed.
I changed my patch to implement the change you have suggested. Basically I return 'iounit' as 'st_blksize' and in 'st_blocks' I return the number of iounit blocks required to fit st_size of the file. The following patches are diffs from my old patch. They require the iounit patches that Mohan has sent to this list on 4th.
Comments welcome. Specifically please look at the changes in v9fs_getattr_post_lstat() below.
Thanks,
Sripathi.
Kernel patch:
=============
Fix block size of getattr call. Depends on Mohan's iounit patch.
---
fs/9p/vfs_inode.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
fs/9p/vfs_inode.c +2 -0
@@ -955,6 +955,8 @@ v9fs_vfs_getattr_dotl(struct vfsmount *mnt, struct dentry *dentry,v9fs_stat2inode_dotl (st, dentry->d_inode);generic_fillattr (dentry->d_inode, stat); +/* Change block size to what the server returned */ + stat->blksize = st->st_blksize;kfree (st);return 0 ;
QEMU patch:
===========
Fix block size of getattr call. Depends on Mohan's iounit patch.
---
hw/virtio-9p.c | 55 +++++++++++++++++++++++++++++++------------------------ hw/virtio-9p.h | 1 + 2 files changed, 32 insertions(+), 24 deletions(-)
hw/virtio-9p.c +31 -24
90 lines not on this page · raw message
hw/virtio-9p.h +1 -0
@@ -211,6 +211,7 @@ typedef struct V9fsStatDotl {typedef struct V9fsStatStateDotl {V9fsPDU *pdu;size_t offset; +V9fsFidState *fidp;V9fsStatDotl v9stat_dotl;struct stat stbuf; }V9fsStatStateDotl ;
On Mon, 7 Jun 2010 16:04:17 +0530
Sripathi Kodi <[email protected]> wrote:
There was one mistake in my patch. See below.
Quoted 175 lines
Quoted 69 lines · On Sat, 05 Jun 2010 19:11:53 +0530 "Aneesh Kumar K. V"…
Quoted 68 lines · Venkateswararao Jujjuri (JV)
Quoted 66 lines · Aneesh Kumar K. V
Quoted 56 lines · Sripathi Kodi
Quoted 41 lines · On Wed, 02 Jun 2010 19:49:24 +0530 "Aneesh Kumar K. V"…
Quoted 40 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)Quoted 7 lines
Quoted 5 lines
st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOSo it should be scaled by iounit right ? If we say 9p block size is iounit.
Yes, I think it should be iounit. Currently
st_blksizebeing returned in stat structure to the user space does not use this field that comes from the server. It is being calculated as follows ingeneric_fillattr():Quoted 5 lines
stat->blksize = (1 << inode->i_blkbits);So there may not be a need to put
st_blksizeon the protocol. Further,inode->i_blkbitsis copied fromsb->s_blocksize_bits. For 9P this value is obtained as:That is what linux kernel currently does. But from the protocol point of view and not looking at specific linux implementation i would suggest to put
st_blksizeon wire.Quoted 8 lines
Quoted 3 lines
This is part of .L protocol. Specifically for Linux systems. So, if Linux is already doing it, I don't think we need to repeat it.
But nothing prevents from changing Linux internal implementation. So we can't depend on Linux kernel internal implementation. Later in 2.6.x we may not derive
stat->blksizefrominode->i_blkbitsat all. So we cannot depend on Linux kernel internal implementation.Okay, agreed.
I changed my patch to implement the change you have suggested. Basically I return 'iounit' as '
st_blksize' and in 'st_blocks' I return the number of iounit blocks required to fitst_sizeof the file. The following patches are diffs from my old patch. They require the iounit patches that Mohan has sent to this list on 4th.Comments welcome. Specifically please look at the changes in
v9fs_getattr_post_lstat()below.Thanks,
Sripathi.Kernel patch:
=============Fix block size of getattr call. Depends on Mohan's iounit patch.
Signed-off-by Sripathi Kodi <[email protected]>---
fs/9p/vfs_inode.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)fs/9p/vfs_inode.c +2
-0@@ -955,6 +955,8 @@ v9fs_vfs_getattr_dotl(struct vfsmount *mnt, struct dentry *dentry,v9fs_stat2inode_dotl (st, dentry->d_inode);generic_fillattr (dentry->d_inode, stat); +/* Change block size to what the server returned */ + stat->blksize = st->st_blksize;kfree (st);return 0 ;QEMU patch:
===========Fix block size of getattr call. Depends on Mohan's iounit patch.
Signed-off-by Sripathi Kodi <[email protected]>---
hw/virtio-9p.c | 55 +++++++++++++++++++++++++++++++------------------------ hw/virtio-9p.h | 1 + 2 files changed, 32 insertions(+), 24 deletions(-)hw/virtio-9p.c +20
-0@@ -1180,6 +1180,26 @@ out:qemu_free (vs); } +static int32_t get_iounit (V9fsState *s,V9fsString *name) +{ +struct statfs stbuf; +int32_t iounit =0 ; + +/* +* iounit should be multiples of f_bsize (host filesystem block size +* and as well as less than (client msize - P9_IOHDRSZ)) +*/ +if (!v9fs_do_statfs (s, name, &stbuf)) { + iounit = stbuf.f_bsize; + iounit *= (s->msize -P9_IOHDRSZ )/stbuf.f_bsize; + } + +if (!iounit) { + iounit = s->msize -P9_IOHDRSZ ; + } +return iounit; +} +static void v9fs_getattr_post_lstat (V9fsState *s,V9fsStatStateDotl *vs,int err) {@@ -1188,7 +1208,15 @@ static void v9fs_getattr_post_lstat(V9fsState *s, V9fsStatStateDotl *vs, goto out; }
hw/virtio-9p.c static void v9fs_getattr_post_lstat(V9fsState *s, V9fsStatStateDotl *vs, · line 1219
Quoted 10 lines
hw/virtio-9p.c +8
-0+/* Recalculate block size and number of blocks based on iounit */ stat_to_v9stat_dotl (s, &vs->stbuf, &vs->v9stat_dotl); + vs->v9stat_dotl.st_blksize =get_iounit (s, &vs->fidp->path); + vs->v9stat_dotl.st_blocks = vs->v9stat_dotl.st_size / + vs->v9stat_dotl.st_blksize; +if (vs->v9stat_dotl.st_size % vs->v9stat_dotl.st_blksize) { + vs->v9stat_dotl.st_blocks++; + } +
I should not update st_blocks when I update st_blksize. This is because from the manpage, st_blocks is always number of 512 byte blocks needed for this file.
blkcnt_t st_blocks; /* number of 512B blocks allocated */
Hence by changing st_blocks user space tools like 'du' go wrong.
Thanks,
Sripathi.
Quoted 77 lines
hw/virtio-9p.c +3
-24vs->offset +=pdu_marshal (vs->pdu, vs->offset,"A" , &vs->v9stat_dotl); err = vs->offset;@@ -1202,7 +1230,6 @@ static void v9fs_getattr(V9fsState *s, V9fsPDU *pdu)int32_t fid;V9fsStatStateDotl *vs;ssize_t err =0 ; -V9fsFidState *fidp; vs =qemu_malloc (sizeof (*vs)); vs->pdu = pdu;@@ -1212,13 +1239,13 @@ static void v9fs_getattr(V9fsState *s, V9fsPDU *pdu)pdu_unmarshal (vs->pdu, vs->offset,"d" , &fid); - fidp =lookup_fid (s, fid); -if (fidp ==NULL ) { + vs->fidp =lookup_fid (s, fid); +if (vs->fidp ==NULL ) { err = -ENOENT ; goto out; } - err =v9fs_do_lstat (s, &fidp->path, &vs->stbuf); + err =v9fs_do_lstat (s, &vs->fidp->path, &vs->stbuf);v9fs_getattr_post_lstat (s, vs, err);return ;@@ -1390,26 +1417,6 @@ out:v9fs_walk_complete (s, vs, err); } -static int32_t get_iounit (V9fsState *s,V9fsString *name) -{ -struct statfs stbuf; -int32_t iounit =0 ; - -/* -* iounit should be multiples of f_bsize (host filesystem block size -* and as well as less than (client msize - P9_IOHDRSZ)) -*/ -if (!v9fs_do_statfs (s, name, &stbuf)) { - iounit = stbuf.f_bsize; - iounit *= (s->msize -P9_IOHDRSZ )/stbuf.f_bsize; - } - -if (!iounit) { - iounit = s->msize -P9_IOHDRSZ ; - } -return iounit; -} -static void v9fs_open_post_opendir (V9fsState *s,V9fsOpenState *vs,int err) {if (vs->fidp->dir ==NULL ) {hw/virtio-9p.h +1
-1@@ -211,6 +211,7 @@ typedef struct V9fsStatDotl {typedef struct V9fsStatStateDotl {V9fsPDU *pdu;size_t offset; +V9fsFidState *fidp;V9fsStatDotl v9stat_dotl;struct stat stbuf; }V9fsStatStateDotl ; ------------------------------------------------------------------------------ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
V9fs-developer mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/v9fs-developer
Quoted 78 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOst_blocks[8]
Number of file system blocks allocatedst_atime_sec[8]
Time of last access, secondsst_atime_nsec[8]
Time of last access, nanosecondsst_mtime_sec[8]
Time of last modification, secondsst_mtime_nsec[8]
Time of last modification, nanosecondsst_ctime_sec[8]
Time of last status change, secondsst_ctime_nsec[8]
Time of last status change, nanosecondsThis patch implements the client side of getattr implementation for 9P2000.L. It introduces a new structure
p9_stat_dotlfor getting Linux stat information along with QID. The data layout is similar to stat structure in Linux user space with the following major differences:inode (
st_ino) is not part of data. Instead qid is.device (
st_dev) is not part of data because this doesn't make sense on the client.
Quoted 8 lines
All time variables are 64 bit wide on the wire. The kernel seems to use 32 bit variables for these variables. However, some of the architectures have used 64 bit variables and glibc exposes 64 bit variables to user space on some architectures. Hence to be on the safer side we have made these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
Can we just hold on this patch. There is a discussion to add i_generation and inode create time to a variant of stat. So may be the protocol bits need those
-aneesh
Quoted 88 lines · On Thu, 01 Jul 2010 11:01:15 +0530 "Aneesh Kumar K. V"…
Quoted 78 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOst_blocks[8]
Number of file system blocks allocatedst_atime_sec[8]
Time of last access, secondsst_atime_nsec[8]
Time of last access, nanosecondsst_mtime_sec[8]
Time of last modification, secondsst_mtime_nsec[8]
Time of last modification, nanosecondsst_ctime_sec[8]
Time of last status change, secondsst_ctime_nsec[8]
Time of last status change, nanosecondsThis patch implements the client side of getattr implementation for 9P2000.L. It introduces a new structure
p9_stat_dotlfor getting Linux stat information along with QID. The data layout is similar to stat structure in Linux user space with the following major differences:inode (
st_ino) is not part of data. Instead qid is.device (
st_dev) is not part of data because this doesn't make sense on the client.Quoted 8 lines
All time variables are 64 bit wide on the wire. The kernel seems to use 32 bit variables for these variables. However, some of the architectures have used 64 bit variables and glibc exposes 64 bit variables to user space on some architectures. Hence to be on the safer side we have made these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.h
Quoted 4 lines
Can we just hold on this patch. There is a discussion to add
i_generationand inode create time to a variant of stat. So may be the protocol bits need those
IMHO, we can put this in now and change it later if needed based on how the discussion about VFS changes go because:
a) 9P2000.L is still at experimental stage, so it allows us to change the protocol later.
b) The kernel patch for this is already in linux-next. Without these patches in QEMU it won't be possible to use 9P2000.L.
Thanks,
Sripathi.
Quoted 2 lines
-aneesh
Quoted 96 lines · Sripathi Kodi
Quoted 88 lines · On Thu, 01 Jul 2010 11:01:15 +0530 "Aneesh Kumar K. V"…
Quoted 78 lines · Sripathi Kodi
From: M. Mohan Kumar <[email protected]>
SYNOPSIS
size[4] Tgetattr tag[2] fid[4]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid. The reply will contain a machine-independent directory entry, laid out as follows:
qid.type[1]
the type of the file (directory, etc.), represented as a bit vector corresponding to the high 8 bits of the file's mode word.qid.vers[4]
version number for given pathqid.path[8]
the file server's unique identification for the filest_mode[4]
Permission and flagsst_nlink[8]
Number of hard linksst_uid[4]
User id of ownerst_gid[4]
Group ID of ownerst_rdev[8]
Device ID (if special file)st_size[8]
Size, in bytesst_blksize[8]
Block size for file system IOst_blocks[8]
Number of file system blocks allocatedst_atime_sec[8]
Time of last access, secondsst_atime_nsec[8]
Time of last access, nanosecondsst_mtime_sec[8]
Time of last modification, secondsst_mtime_nsec[8]
Time of last modification, nanosecondsst_ctime_sec[8]
Time of last status change, secondsst_ctime_nsec[8]
Time of last status change, nanosecondsThis patch implements the client side of getattr implementation for 9P2000.L. It introduces a new structure
p9_stat_dotlfor getting Linux stat information along with QID. The data layout is similar to stat structure in Linux user space with the following major differences:inode (
st_ino) is not part of data. Instead qid is.device (
st_dev) is not part of data because this doesn't make sense on the client.Quoted 8 lines
All time variables are 64 bit wide on the wire. The kernel seems to use 32 bit variables for these variables. However, some of the architectures have used 64 bit variables and glibc exposes 64 bit variables to user space on some architectures. Hence to be on the safer side we have made these 64 bit in the protocol. Refer to the comments in
include/asm-generic/stat.hQuoted 4 lines
Can we just hold on this patch. There is a discussion to add
i_generationand inode create time to a variant of stat. So may be the protocol bits need those
Quoted 7 lines
IMHO, we can put this in now and change it later if needed based on how the discussion about VFS changes go because:
a) 9P2000.L is still at experimental stage, so it allows us to change the protocol later.
b) The kernel patch for this is already in linux-next. Without these patches in QEMU it won't be possible to use 9P2000.L.
The comment was w.r.t kernel and qemu patches. I am not sure whether we would reach a conclusion about how the syscall interface soon. But i guess BSD already support birth time. So in any way having a protocol update to support i_generation and birth time is a good thing to do, because we already know that NFS and CIFS would need it from a file system.
-aneesh