2005-09-10 04:04:20 +08:00
|
|
|
/*
|
|
|
|
|
* V9FS VFS extensions.
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 2004 by Eric Van Hensbergen <ericvh@gmail.com>
|
|
|
|
|
* Copyright (C) 2002 by Ron Minnich <rminnich@lanl.gov>
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
2006-03-25 19:07:28 +08:00
|
|
|
* it under the terms of the GNU General Public License version 2
|
|
|
|
|
* as published by the Free Software Foundation.
|
2005-09-10 04:04:20 +08:00
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
|
* along with this program; if not, write to:
|
|
|
|
|
* Free Software Foundation
|
|
|
|
|
* 51 Franklin Street, Fifth Floor
|
|
|
|
|
* Boston, MA 02111-1301 USA
|
|
|
|
|
*
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* plan9 semantics are that created files are implicitly opened.
|
|
|
|
|
* But linux semantics are that you call create, then open.
|
|
|
|
|
* the plan9 approach is superior as it provides an atomic
|
|
|
|
|
* open.
|
|
|
|
|
* we track the create fid here. When the file is opened, if fidopen is
|
|
|
|
|
* non-zero, we use the fid and can skip some steps.
|
|
|
|
|
* there may be a better way to do this, but I don't know it.
|
|
|
|
|
* one BAD way is to clunk the fid on create, then open it again:
|
|
|
|
|
* you lose the atomicity of file open
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* special case:
|
|
|
|
|
* unlink calls remove, which is an implicit clunk. So we have to track
|
|
|
|
|
* that kind of thing so that we don't try to clunk a dead fid.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
extern struct file_system_type v9fs_fs_type;
|
2006-06-28 19:26:44 +08:00
|
|
|
extern const struct address_space_operations v9fs_addr_operations;
|
2006-03-28 17:56:42 +08:00
|
|
|
extern const struct file_operations v9fs_file_operations;
|
2010-03-25 20:41:54 +08:00
|
|
|
extern const struct file_operations v9fs_file_operations_dotl;
|
2006-03-28 17:56:42 +08:00
|
|
|
extern const struct file_operations v9fs_dir_operations;
|
2010-03-25 20:41:54 +08:00
|
|
|
extern const struct file_operations v9fs_dir_operations_dotl;
|
2009-02-20 13:55:46 +08:00
|
|
|
extern const struct dentry_operations v9fs_dentry_operations;
|
|
|
|
|
extern const struct dentry_operations v9fs_cached_dentry_operations;
|
2005-09-10 04:04:20 +08:00
|
|
|
|
2009-09-24 02:00:27 +08:00
|
|
|
#ifdef CONFIG_9P_FSCACHE
|
|
|
|
|
struct inode *v9fs_alloc_inode(struct super_block *sb);
|
|
|
|
|
void v9fs_destroy_inode(struct inode *inode);
|
|
|
|
|
#endif
|
|
|
|
|
|
2005-09-10 04:04:20 +08:00
|
|
|
struct inode *v9fs_get_inode(struct super_block *sb, int mode);
|
2010-06-08 02:34:48 +08:00
|
|
|
void v9fs_evict_inode(struct inode *inode);
|
2007-07-11 06:57:28 +08:00
|
|
|
ino_t v9fs_qid2ino(struct p9_qid *qid);
|
2008-10-16 21:30:07 +08:00
|
|
|
void v9fs_stat2inode(struct p9_wstat *, struct inode *, struct super_block *);
|
9p: getattr client implementation for 9P2000.L protocol.
SYNOPSIS
size[4] Tgetattr tag[2] fid[4] request_mask[8]
size[4] Rgetattr tag[2] lstat[n]
DESCRIPTION
The getattr transaction inquires about the file identified by fid.
request_mask is a bit mask that specifies which fields of the
stat structure is the client interested in.
The reply will contain a machine-independent directory entry,
laid out as follows:
st_result_mask[8]
Bit mask that indicates which fields in the stat structure
have been populated by the server
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_uid[4]
User id of owner
st_gid[4]
Group ID of owner
st_nlink[8]
Number of hard links
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
st_btime_sec[8]
Time of creation (birth) of file, seconds
st_btime_nsec[8]
Time of creation (birth) of file, nanoseconds
st_gen[8]
Inode generation
st_data_version[8]
Data version number
request_mask and result_mask bit masks contain the following bits
#define P9_STATS_MODE 0x00000001ULL
#define P9_STATS_NLINK 0x00000002ULL
#define P9_STATS_UID 0x00000004ULL
#define P9_STATS_GID 0x00000008ULL
#define P9_STATS_RDEV 0x00000010ULL
#define P9_STATS_ATIME 0x00000020ULL
#define P9_STATS_MTIME 0x00000040ULL
#define P9_STATS_CTIME 0x00000080ULL
#define P9_STATS_INO 0x00000100ULL
#define P9_STATS_SIZE 0x00000200ULL
#define P9_STATS_BLOCKS 0x00000400ULL
#define P9_STATS_BTIME 0x00000800ULL
#define P9_STATS_GEN 0x00001000ULL
#define P9_STATS_DATA_VERSION 0x00002000ULL
#define P9_STATS_BASIC 0x000007ffULL
#define P9_STATS_ALL 0x00003fffULL
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
There are some additional fields: st_btime_sec, st_btime_nsec, st_gen,
st_data_version apart from the bitmask, st_result_mask. The bit mask
is filled by the server to indicate which stat fields have been
populated by the server. Currently there is no clean way for the
server to obtain these additional fields, so it sends back just the
basic fields.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Eric Van Hensbegren <ericvh@gmail.com>
2010-07-12 22:37:23 +08:00
|
|
|
void v9fs_stat2inode_dotl(struct p9_stat_dotl *, struct inode *);
|
2005-09-10 04:04:20 +08:00
|
|
|
int v9fs_dir_release(struct inode *inode, struct file *filp);
|
|
|
|
|
int v9fs_file_open(struct inode *inode, struct file *file);
|
2008-10-16 21:30:07 +08:00
|
|
|
void v9fs_inode2stat(struct inode *inode, struct p9_wstat *stat);
|
2008-06-25 06:39:39 +08:00
|
|
|
int v9fs_uflags2omode(int uflags, int extended);
|
2008-10-14 09:36:16 +08:00
|
|
|
|
|
|
|
|
ssize_t v9fs_file_readn(struct file *, char *, char __user *, u32, u64);
|
2010-02-09 05:36:48 +08:00
|
|
|
void v9fs_blank_wstat(struct p9_wstat *wstat);
|
2010-09-28 02:57:40 +08:00
|
|
|
int v9fs_vfs_setattr_dotl(struct dentry *, struct iattr *);
|
2010-10-23 01:13:12 +08:00
|
|
|
int v9fs_file_fsync_dotl(struct file *filp, int datasync);
|
9p: Implement TLOCK
Synopsis
size[4] TLock tag[2] fid[4] flock[n]
size[4] RLock tag[2] status[1]
Description
Tlock is used to acquire/release byte range posix locks on a file
identified by given fid. The reply contains status of the lock request
flock structure:
type[1] - Type of lock: F_RDLCK, F_WRLCK, F_UNLCK
flags[4] - Flags could be either of
P9_LOCK_FLAGS_BLOCK - Blocked lock request, if there is a
conflicting lock exists, wait for that lock to be released.
P9_LOCK_FLAGS_RECLAIM - Reclaim lock request, used when client is
trying to reclaim a lock after a server restrart (due to crash)
start[8] - Starting offset for lock
length[8] - Number of bytes to lock
If length is 0, lock all bytes starting at the location 'start'
through to the end of file
pid[4] - PID of the process that wants to take lock
client_id[4] - Unique client id
status[1] - Status of the lock request, can be
P9_LOCK_SUCCESS(0), P9_LOCK_BLOCKED(1), P9_LOCK_ERROR(2) or
P9_LOCK_GRACE(3)
P9_LOCK_SUCCESS - Request was successful
P9_LOCK_BLOCKED - A conflicting lock is held by another process
P9_LOCK_ERROR - Error while processing the lock request
P9_LOCK_GRACE - Server is in grace period, it can't accept new lock
requests in this period (except locks with
P9_LOCK_FLAGS_RECLAIM flag set)
Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
2010-09-27 14:04:24 +08:00
|
|
|
|
|
|
|
|
#define P9_LOCK_TIMEOUT (30*HZ)
|