linux-toradex.git/fs/9p, branch v3.0.95

fs/9p: Use protocol-defined value for lock/getlock 'type' field.

2011-10-03T18:40:22+00:00

commit 51b8b4fb32271d39fbdd760397406177b2b0fd36 upstream.

Signed-off-by: Jim Garlick 
Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Harsh Prateek Bora 
Signed-off-by: Greg Kroah-Hartman

fs/9p: Always ask new inode in lookup for cache mode disabled

2011-10-03T18:40:22+00:00

commit 73f507171cfa407b19f254aef95cbb058c8180cf upstream.

This make sure we don't end up reusing the unlinked inode object.
The ideal way is to use inode i_generation. But i_generation is
not available in userspace always.

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Greg Kroah-Hartman

fs/9p: Add OS dependent open flags in 9p protocol

2011-10-03T18:40:21+00:00

commit f88657ce3f9713a0c62101dffb0e972a979e77b9 upstream.

Some of the flags are OS/arch dependent we add a 9p
protocol value which maps to asm-generic/fcntl.h values in Linux
Based on the original patch from Venkateswararao Jujjuri 

[extra comments from author as to why this needs to go to stable:

Earlier for different operation such as open we used the values of open
flag as defined by the OS.  But some of these flags such as O_DIRECT are
arch dependent. So if we have the 9p client and server running on
different architectures, we end up with client sending client
architecture value of these open flag and server will try to map these
values to what its architecture states. For ex: O_DIRECT on a x86 client
maps to

#define O_DIRECT        00040000

Where as on sparc server it will maps to

#define O_DIRECT        0x100000

Hence we need to map these open flags to OS/arch independent flag
values.  Getting these changes to an early version of kernel ensures us
that we work with different combination of client and server. We should
ideally backport this patch to all possible kernel version.]

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Harsh Prateek Bora 
Signed-off-by: Greg Kroah-Hartman

fs/9p: Don't update file type when updating file attributes

2011-10-03T18:40:21+00:00

commit 45089142b1497dab2327d60f6c71c40766fc3ea4 upstream.

We should only update attributes that we can change on stat2inode.
Also do file type initialization in v9fs_init_inode.

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Eric Van Hensbergen 
Signed-off-by: Greg Kroah-Hartman

fs/9p: Add fid before dentry instantiation

2011-10-03T18:40:21+00:00

commit 5441ae5eb3614d3c28f77073370738a2820c88e4 upstream.

d_instantiate marks the dentry positive. So a parallel lookup and mkdir of
the directory can find dentry that doesn't have fid attached. This can result
in both the code path doing v9fs_fid_add which results in v9fs_dentry leak.

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Eric Van Hensbergen 
Signed-off-by: Greg Kroah-Hartman

9p: close ACL leaks

2011-10-03T18:40:19+00:00

commit 1ec95bf34d976b38897d1977b155a544d77b05e7 upstream.

Signed-off-by: Al Viro 
Signed-off-by: Greg Kroah-Hartman

fs/9p: Always ask new inode in create

2011-10-03T18:40:18+00:00

commit ed80fcfac2565fa866d93ba14f0e75de17a8223e upstream.

This make sure we don't end up reusing the unlinked inode object.
The ideal way is to use inode i_generation. But i_generation is
not available in userspace always.

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Eric Van Hensbergen 
Signed-off-by: Greg Kroah-Hartman

fs/9p: Fix invalid mount options/args

2011-10-03T18:40:18+00:00

commit a2dd43bb0d7b9ce28f8a39254c25840c0730498e upstream.

Without this fix, if any invalid mount options/args are passed while mouting
the 9p fs, no error (-EINVAL) is returned and default arg value is assigned.

This fix returns -EINVAL when an invalid arguement is found while parsing
mount options.

Signed-off-by: Prem Karat 
Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Eric Van Hensbergen 
Signed-off-by: Greg Kroah-Hartman

fs/9p: When doing inode lookup compare qid details and inode mode bits.

2011-10-03T18:40:18+00:00

commit fd2421f54423f307ecd31bdebdca6bc317e0c492 upstream.

This make sure we don't use wrong inode from the inode hash. The inode number
of the file deleted is reused by the next file system object created
and if we only use inode number for inode hash lookup we could end up
with wrong struct inode.

Also compare inode generation number. Not all Linux file system provide
st_gen in userspace. So it could be 0;

Signed-off-by: Aneesh Kumar K.V 
Signed-off-by: Eric Van Hensbergen 
Signed-off-by: Greg Kroah-Hartman

9p: remove unnecessary dentry_unhash on rmdir, dir rename

2011-05-28T05:02:53+00:00

9p has no problems with references to unlinked directories.

CC: Eric Van Hensbergen 
CC: Ron Minnich 
CC: Latchesar Ionkov 
CC: v9fs-developer@lists.sourceforge.net
Signed-off-by: Sage Weil 
Signed-off-by: Al Viro