glusterfs.git/xlators/mount/fuse/src/fuse-resolve.c, branch v3.5beta1

mount/fuse: perform lookup() on inodes linked through readdirplus

2013-08-23T19:09:58+00:00

Some xlators still require lookup() fop to be sent for proper working.
This patch remembers inodes which have been linked through readdiprlus
and makes the resolver send lookups on them.

Change-Id: Ibe8a04a659539d90dfc794521b51bf2bda017a0b
BUG: 979910
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5267
Reviewed-by: Amar Tumballi 
Tested-by: Gluster Build System

fuse-bridge: fix posix-only configuration

2012-11-19T09:17:47+00:00

Recent changes in fuse-resolver had broken the use case of having
a trivial configuration with only storage/posix translator. Fix
it and include a regression test to avoid breakage in the future.

Change-Id: I85cbcac4b5c2d3517dd03fd3dc6d07610697981b
BUG: 868478
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/4114
Tested-by: Gluster Build System 
Reviewed-by: Brian Foster 
Reviewed-by: Vijay Bellur

fuse: create a new fd during fd-migration.

2012-10-02T21:18:14+00:00

Migration of fd to new graph involves creation of a new fd
to be used only for calls sent in that graph.

Earlier approach of using same fd across all graphs, with the
associated inode always guaranteed to be the one valid in
currently active graph, had issues because of the broken
immutability of the association of fd with an inode
(for the life of fd).

With this patch, there will be a basefd, which the kernel will be
aware of. This basefd, contains a mapping of an fd which is valid
in currently active graph.

Signed-off-by: Raghavendra G 
Change-Id: I2b459f05bc2690a66498be107fad6444e3158138
BUG: 802414
Reviewed-on: http://review.gluster.org/3566
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

All: License message change

2012-09-13T20:19:37+00:00

License message changed for server-side, dual license GPLV2 and LGPLv3+.

Change-Id: Ia9e53061b9d2df3b3ef3bc9778dceff77db46a09
BUG: 852318
Signed-off-by: Varun Shastry 
Reviewed-on: http://review.gluster.org/3940
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Anand Avati

All: License message change

2012-08-28T10:45:06+00:00

The license message is changed to
  Copyright (c) 2008-2012 Red Hat, Inc. 
  This file is part of GlusterFS.

  This file is licensed to you under your choice of the GNU Lesser
  General Public License, version 3 or any later version (LGPLv3 or
  later), or the GNU General Public License, version 2 (GPLv2), in all
  cases as published by the Free Software Foundation.

Change-Id: I07d2b63ed5fbbbd1884f1e74f2dd56013d15b0f4
BUG: 852318
Signed-off-by: Varun Shastry 
Reviewed-on: http://review.gluster.org/3858
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mount/fuse: ignore any erros that might've happened while resolving entry in resolver.

2012-08-03T08:13:36+00:00

One error we hit was absence of gfid on backend. While the lookup
code-path generates a new uuid and sets it on file, resolver code
doesn't do that. Since, functionally (atleast after resolving parent
inode, we would be resolving the path in new-graph) both resolver
and lookup does same work, it would be no harm in ignoring errors
during resolving the entry. This would help us to continue with
the _extra_ work (like healing gfid as of now) in fuse_lookup_resume.

Change-Id: If46d5e07c32e67b5744287a6ef55d0b0fe347689
BUG: 821138
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/3344
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

fuse-resolve: consider cases where an entry should be resolved even when parent belongs to active itable.

2012-08-03T07:33:48+00:00

When parent is root, the parent inode returned will always be
active_subvol->itable->root and hence there can be cases where we
should explicitly resolve the entry in active graph.

BUG: 804592
Change-Id: I5829278e27435e06785a923ce8776616cedfb519
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/3710
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Revert "fuse-resolve: consider cases where an entry should be resolved even when parent belongs to active itable."

2012-05-23T19:21:51+00:00

This reverts commit 595bc33c1d0a3a6fe3d54d3eb876ac0b336d9dea

Change-Id: I6c67404d4ff0bc83cfac83d786bc6e66d221a84a
Reviewed-on: http://review.gluster.com/3422
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

fuse-resolve: Attempt fd-migration in resolver, if migration

2012-05-16T00:09:58+00:00

was never attempted.

Since fd is always associated with an inode, we can create an
fd only after resolver resolves an inode. So, there is a possibility
that graph-switch can happen after resolver kicks in, but before
it can complete, thereby resulting in the newly created fd not
migrated to new graph. So, instead of migrating fds only during
graph-switch, we give a second chance during fd-resolution.

As an example, consider following sequence of events during a
create call:
1. create wants to resolve parent inode, hence it starts
   resolution for parent
2. graph-switch happens (it can happen since fuse-request reader
   thread returns after winding lookup calls)
3. fd-migration of all the fds which are currently in fdtable is
   attempted (Note that the fd corresponding to current create call
   is not yet created and added to fd-table, hence it will not be
   migrated as part of graph switch)
4. resolution of parent triggered as part of create, completes
5. fd is created in fuse_create_resume and this fd is not migrated
   to new graph
6. Any future fops on this fd will fail with EBADF errors
   (create call itself will succeed)

Change-Id: Iae06ecfaca24eaacb2e166ffefbbbb57446332ba
BUG: 804592
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/3181
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

fuse-resolve: consider cases where an entry should be resolved even

2012-05-08T22:34:53+00:00

when parent belongs to active itable.

When parent is root, the parent inode returned will always be
active_subvol->itable->root and hence there can be cases where we
should explicitly resolve the entry in active graph.

Change-Id: I4e82df9a351ff6b5304891abc9932495bf7ea79d
BUG: 804592
Signed-off-by: Raghavendra G 
Reviewed-on: http://review.gluster.com/3007
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati