glusterfs.git/xlators, branch v3.3.0qa2

cluster/afr: read_child should be >= 0

2011-08-13T16:27:09+00:00

Change-Id: I447fb6a93cdd77de322cd5ded30673411c4cf79e
BUG: 3251
Reviewed-on: http://review.gluster.com/233
Reviewed-by: Vijay Bellur 
Tested-by: Gluster Build System

- Use linkat(2) instead of link(2) so that linking to symlink work on

2011-08-12T13:51:01+00:00

non Linux systems
- Also use mkfifo to create FIFO on NetBSD: it does not wotk with mknod

Change-Id: I19ffd22b4d79009ef5f9d4a50fc6dd556c3c3ff4
BUG: 2923
Reviewed-on: http://review.gluster.com/226
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

For systems where O_DIRECTORY does not exist, we defined it as 0,

2011-08-12T12:03:15+00:00

therefore ((flags & O_DIRECTORY) == O_DIRECTORY) is always true even
if the flag is not set.

Change-Id: Ie7837d521ea20b36ed70cf93c1763c226ff0e9f0
BUG: 2923
Reviewed-on: http://review.gluster.com/213
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Do not distribute UFS1 extended attribute backing store

2011-08-12T12:02:58+00:00

Change-Id: Ie05751aa8d96a2f7996843a914e1a66df2777eba
BUG: 2923
Reviewed-on: http://review.gluster.com/222
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

RO: fix read-only xlator support broken due to worm xlator fix

2011-08-11T09:37:22+00:00

Change-Id: I7234909eecdc6af1b8482465f19d0490fcba94ad
BUG: 3166
Reviewed-on: http://review.gluster.com/210
Reviewed-by: Vijay Bellur 
Tested-by: Gluster Build System

WORM: Write Once Read Many times xlator support

2011-08-11T05:51:56+00:00

This xlator will allow files to be opened for write in append mode
only. Mount with --worm(glusterfs) or -o worm (mount) option to
enable worm xlator

Change-Id: I1be02fcf2aee2182ea2c66b514357918136fabeb
BUG: 3166
Reviewed-on: http://review.gluster.com/23
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

posix-acl: disable permission checks for fd based ops

2011-08-11T05:06:56+00:00

If write calls are coming in through an fd with O_RDWR or O_WRONLY
flag then a permission check is unnecessary. However writes from
NFS ideally need a "stateless" check in each call and this results
in a permission failure due to the read-only mode (disregarding the
FD's writeability).

For now it is acceptable to disable write checks as almost always
the NFS client would already be doing such basic access control.
Also because the previous access-control translator (prior to
posix ACL introduction) too was permitting writes and reads
unconditionally.

In fact the Linux KNFS server too assumes the NFS client would have
done the permission check.

Change-Id: I33e5de8911a87881f9341b8b92574780c2dfbeba
BUG: 3388
Reviewed-on: http://review.gluster.com/208
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Change Copyright current year

2011-08-10T17:57:19+00:00

Change-Id: I2d10f2be44f518f496427f257988f1858e888084
BUG: 3348
Reviewed-on: http://review.gluster.com/200
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

fuse-resolve: prevent linking of inodes of different inode-table

2011-08-10T13:53:06+00:00

This can happen in deep_resolve_cbk, which happens after a graph
switch. Root cause was because the graph change happened while
a FOP was in transit and by the time the call came back, the active
translator of fuse is now changed.

Fix is to make sure the resolve operation happens on a given
inode table, instead of taking the latest graph of fuse for
each operation

Change-Id: Idd6e2d5c2d5fc5d571f7a1fbc174e210babf8a2b
BUG: 3355
Reviewed-on: http://review.gluster.com/195
Tested-by: Gluster Build System 
Reviewed-by: Shishir Gowda 
Reviewed-by: Anand Avati

pass xlator pointer to rpcsvc_init() so that it can init svc->mydata to xlator

2011-08-09T09:12:03+00:00

Change-Id: Icfd95cc67400c16a951d6a9f922fbdc07f40c5b6
BUG: 3314
Reviewed-on: http://review.gluster.com/180
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur