CID 72601: remove dead code.
cmake: allow the FSAL_DESTINATION to be overwritten

In certain environments, the library pathes are no longer
lib, lib32, and lib64 - such as Debian based systems that support
multiarch where the library path for the 64-bit architectures
are actually /usr/lib/x86_64-linux-gnu/ganesha and use the gnu
tuple based definition for the library.

So, to maintain backwards compatibility just allow an
override to cmake that can install the FSAL modules into
a different location.

Usage:

$ cmake -DFSAL_DESTINATION=lib/x86_64-linux-gnu/ganesha

Signed-off-by: Charles Hardin <ckhardin@gmail.com>
cmake: use the environment DESTDIR override for python installs

In several packaging steps, the DESTDIR is specified to install
the results to a local directory without changing the prefix
of the compilation.

So, in this case use the DESTDIR for the python installation
command to avoid any attempts to install to the root "/usr"
path when doing package installs.

Signed-off-by: Charles Hardin <ckhardin@gmail.com>
cmake: add a debian cmake build configuration

In the long run, the cmake packager can be used to create the debian
package by adding all of the appropriate glue definitions into this
file.

In the short term, this configuration is just referenced from
the debian/rules to trampoline from a "git-buildpackage" or a
"dpkg-buildpackage" command into the debian specific build
configuration.

Signed-off-by: Charles Hardin <ckhardin@gmail.com>
debian: update the debian configuration for packaging

Update to a 2.1.0 package and remove the specific 1.5.0 patches.

Rough cut, can easily be refined from here

Signed-off-by: Charles Hardin <ckhardin@gmail.com>
fsal-proxy: implement the status() of FSAL API

Now is_open() depends on the status() API to get open flags, so we need a
proper pxy_status().  Otherwise, cache_inode_rdwr_plus() will loop forever as
the default status() returns FSAL_O_CLOSED.

Signed-off-by: Ming Chen <mchen@cs.stonybrook.edu>
fsal-proxy: fix NFS4ERR_BAD_SEQID in pxy_create()

As ffilz pointed out long time ago in
http://sourceforge.net/p/nfs-ganesha/mailman/message/30876823,
pxy_create() mistakes stateid->seqid for open owner seqid and causes
NFS4ERR_BAD_SEQID errors.

This patch maintains an open owner seqid in the client side (proxy FSAL in this
case), and increments the open owner seqid upon state mutating operations
(OPEN, OPEN_CONFIRM, and CLOSE).

Signed-off-by: Ming Chen <mchen@cs.stonybrook.edu>
uid2grp: make it static like other support libs

Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr>
FSAL LUSTRE: store fsid in handle instead of dev_t

Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr>
Merge remote-tracking branch 'ckhardin/master' into next

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Merge remote-tracking branch 'sbu-fsl/next' into next

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Merge remote-tracking branch 'marc/CID72601' into next

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Merge remote-tracking branch 'martinetd/next' into next

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
V2.2-dev-9

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
fsal_up: Fixed an issue in upcall "invalidate_close"

During cache_inode_entry invalidation upcall, make a synchronous
call of cache_inode_invalidate() only if there are no open/active fds
for the object handle of that entry.

Signed-off-by: Soumya Koduri <skoduri@redhat.com>
cache_inode: correct confusing log messages

Signed-off-by: Niels de Vos <ndevos@redhat.com>
Acked-by: Frank S. Filz <ffilzlnx@mindspring.com>
Acked-by: Malahal Naineni <malahal@us.ibm.com>
Acked-by: Venkateswararao Jujjuri (JV) <jvrao@linux.vnet.ibm.com>
Acked-by: Soumya Koduri <skoduri@redhat.com>
Merge remote-tracking branch 'ndevos/trivial/logging/cache_inode_setattr' into next

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Merge remote-tracking branch 'remotes/skoduri/fsal_up' into next

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Convert FSAL_VFS/panfs to work with the new pnfs_device format.

The pnfs_device format recently changed to have structure in the first
64-bits, as opposed to storing an export ID in that field.  Convert the
panfs implementation in FSAL_VFS to use this new format.

Signed-off-by: Daniel Gryniewicz <dang@linuxbox.com>
Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
Merge branch 'panfs' into next

Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>