glusterfs.git/xlators/mount, branch v3.0.0

fix typo in 76d6f3fbe

2009-12-07T06:16:58+00:00

Signed-off-by: Csaba Henk 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

fuse-bridge: set lk_owner to -1 for release forged flush.

2009-12-06T20:39:19+00:00

Server would interpret 0 as a sign of us getting disconnected.

Signed-off-by: Csaba Henk 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

fuse-bridge: make use of lock owner data in a protocol adherent way.

2009-12-06T20:39:15+00:00

No need for pid fallback, for those cases where we use it,
it's always available.

It appears conditionally in read/write/truncate (related to mandatory
locking). There just get it for demonstrative purposes.

Discard it from release, there locking data exists only as a
portability hack, no use of it on Linux.

Signed-off-by: Csaba Henk 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

fuse-bridge: log cases where newer generation is found in table

2009-12-06T18:35:06+00:00

This is usually the case when there is a bug a cluster xlator and returns
generation number from the wrong subvolume

Signed-off-by: Anand V. Avati 
Signed-off-by: Anand V. Avati 

BUG: 433 (Posix conformance test failed on 3.0.0pre2 (Dec 3) release)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=433

fuse: fix leak in fuse_getxattr and fuse_getattr

2009-12-05T11:41:30+00:00

In fuse_getxattr, @finh was leaked in the case of posix ACL getxattr
request

In fuse_getattr, @state was leaked when fuse_loc_fill() failed

Signed-off-by: Anand V. Avati 
Signed-off-by: Anand V. Avati 

BUG: 438 (Memory leak)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=438

mount/fuse: Refactored fuse_setattr.

2009-12-04T13:26:30+00:00

If both truncate & setattr need to be sent from fuse_setattr,
they are now sent one after the other (setattr first, and then truncate)
instead of being sent parallelly. The earlier code that sent them parallelly
had a couple of problems:

1) A bug in the logic that would sometimes cause the setattr call
   to never return, making the application hang.

2) A possibility that truncate and setattr would race at the server/io-threads/posix
   end, thus returning the wrong stat structure to the application.

This patch also removes an unneccessary "can_fuse_return" call in
fuse_attr_cbk, which would cause a call to hang if STAT or FSTAT failed.

Signed-off-by: Vikas Gorur 
Signed-off-by: Anand V. Avati 

BUG: 146 (Add setattr FOP)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

mount/fuse: Print correct log message if encountered with errno - EAGAIN.

2009-12-03T20:45:18+00:00

Signed-off-by: Pavan Vilas Sondur 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

mount/fuse: Use fuse lock_owner field in posix locks.

2009-12-03T20:44:52+00:00

Signed-off-by: Pavan Vilas Sondur 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

mount/fuse: Handle the case when attribute_timeout is set to 0 in dictionary.

2009-12-03T19:49:10+00:00

Signed-off-by: Vijay Bellur 
Signed-off-by: Anand V. Avati 

BUG: 252 (client coherence problem with locks and truncate)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=252

Fixed typo in gf_proc_dump for attribute_timeout.

2009-11-26T10:49:03+00:00

Signed-off-by: Harshavardhana 
Signed-off-by: Anand V. Avati 

BUG: 410 (Typo in gf_proc_dump for attribute_timeout)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=410