License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 08:07:57 -06:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2010-04-06 16:14:15 -06:00
|
|
|
#include <linux/ceph/ceph_debug.h>
|
2009-10-06 12:31:13 -06:00
|
|
|
|
|
|
|
#include <linux/exportfs.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 02:04:11 -06:00
|
|
|
#include <linux/slab.h>
|
2009-10-06 12:31:13 -06:00
|
|
|
#include <asm/unaligned.h>
|
|
|
|
|
|
|
|
#include "super.h"
|
2010-04-06 16:14:15 -06:00
|
|
|
#include "mds_client.h"
|
2009-10-06 12:31:13 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Basic fh
|
|
|
|
*/
|
|
|
|
struct ceph_nfs_fh {
|
|
|
|
u64 ino;
|
|
|
|
} __attribute__ ((packed));
|
|
|
|
|
|
|
|
/*
|
2014-03-01 03:05:41 -07:00
|
|
|
* Larger fh that includes parent ino.
|
2009-10-06 12:31:13 -06:00
|
|
|
*/
|
|
|
|
struct ceph_nfs_confh {
|
|
|
|
u64 ino, parent_ino;
|
|
|
|
} __attribute__ ((packed));
|
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
/*
|
|
|
|
* fh for snapped inode
|
|
|
|
*/
|
|
|
|
struct ceph_nfs_snapfh {
|
|
|
|
u64 ino;
|
|
|
|
u64 snapid;
|
|
|
|
u64 parent_ino;
|
|
|
|
u32 hash;
|
|
|
|
} __attribute__ ((packed));
|
|
|
|
|
|
|
|
static int ceph_encode_snapfh(struct inode *inode, u32 *rawfh, int *max_len,
|
|
|
|
struct inode *parent_inode)
|
|
|
|
{
|
|
|
|
const static int snap_handle_length =
|
|
|
|
sizeof(struct ceph_nfs_snapfh) >> 2;
|
|
|
|
struct ceph_nfs_snapfh *sfh = (void *)rawfh;
|
|
|
|
u64 snapid = ceph_snap(inode);
|
|
|
|
int ret;
|
|
|
|
bool no_parent = true;
|
|
|
|
|
|
|
|
if (*max_len < snap_handle_length) {
|
|
|
|
*max_len = snap_handle_length;
|
|
|
|
ret = FILEID_INVALID;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = -EINVAL;
|
|
|
|
if (snapid != CEPH_SNAPDIR) {
|
|
|
|
struct inode *dir;
|
|
|
|
struct dentry *dentry = d_find_alias(inode);
|
|
|
|
if (!dentry)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
rcu_read_lock();
|
|
|
|
dir = d_inode_rcu(dentry->d_parent);
|
|
|
|
if (ceph_snap(dir) != CEPH_SNAPDIR) {
|
|
|
|
sfh->parent_ino = ceph_ino(dir);
|
|
|
|
sfh->hash = ceph_dentry_hash(dir, dentry);
|
|
|
|
no_parent = false;
|
|
|
|
}
|
|
|
|
rcu_read_unlock();
|
|
|
|
dput(dentry);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (no_parent) {
|
|
|
|
if (!S_ISDIR(inode->i_mode))
|
|
|
|
goto out;
|
|
|
|
sfh->parent_ino = sfh->ino;
|
|
|
|
sfh->hash = 0;
|
|
|
|
}
|
|
|
|
sfh->ino = ceph_ino(inode);
|
|
|
|
sfh->snapid = snapid;
|
|
|
|
|
|
|
|
*max_len = snap_handle_length;
|
|
|
|
ret = FILEID_BTRFS_WITH_PARENT;
|
|
|
|
out:
|
|
|
|
dout("encode_snapfh %llx.%llx ret=%d\n", ceph_vinop(inode), ret);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2012-04-05 13:07:36 -06:00
|
|
|
static int ceph_encode_fh(struct inode *inode, u32 *rawfh, int *max_len,
|
|
|
|
struct inode *parent_inode)
|
2009-10-06 12:31:13 -06:00
|
|
|
{
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
const static int handle_length =
|
|
|
|
sizeof(struct ceph_nfs_fh) >> 2;
|
|
|
|
const static int connected_handle_length =
|
|
|
|
sizeof(struct ceph_nfs_confh) >> 2;
|
2010-10-05 04:33:41 -06:00
|
|
|
int type;
|
2009-10-06 12:31:13 -06:00
|
|
|
|
|
|
|
if (ceph_snap(inode) != CEPH_NOSNAP)
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
return ceph_encode_snapfh(inode, rawfh, max_len, parent_inode);
|
2009-10-06 12:31:13 -06:00
|
|
|
|
2014-03-01 03:05:41 -07:00
|
|
|
if (parent_inode && (*max_len < connected_handle_length)) {
|
|
|
|
*max_len = connected_handle_length;
|
|
|
|
return FILEID_INVALID;
|
|
|
|
} else if (*max_len < handle_length) {
|
|
|
|
*max_len = handle_length;
|
|
|
|
return FILEID_INVALID;
|
|
|
|
}
|
2012-12-18 15:21:23 -07:00
|
|
|
|
2014-03-01 03:05:41 -07:00
|
|
|
if (parent_inode) {
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
struct ceph_nfs_confh *cfh = (void *)rawfh;
|
2014-03-01 03:05:41 -07:00
|
|
|
dout("encode_fh %llx with parent %llx\n",
|
|
|
|
ceph_ino(inode), ceph_ino(parent_inode));
|
2012-04-05 13:07:36 -06:00
|
|
|
cfh->ino = ceph_ino(inode);
|
2014-03-01 03:05:41 -07:00
|
|
|
cfh->parent_ino = ceph_ino(parent_inode);
|
2010-10-05 04:33:41 -06:00
|
|
|
*max_len = connected_handle_length;
|
2014-03-01 03:05:41 -07:00
|
|
|
type = FILEID_INO32_GEN_PARENT;
|
2009-10-06 12:31:13 -06:00
|
|
|
} else {
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
struct ceph_nfs_fh *fh = (void *)rawfh;
|
2014-03-01 03:05:41 -07:00
|
|
|
dout("encode_fh %llx\n", ceph_ino(inode));
|
|
|
|
fh->ino = ceph_ino(inode);
|
2010-10-05 04:33:42 -06:00
|
|
|
*max_len = handle_length;
|
2014-03-01 03:05:41 -07:00
|
|
|
type = FILEID_INO32_GEN;
|
2009-10-06 12:31:13 -06:00
|
|
|
}
|
|
|
|
return type;
|
|
|
|
}
|
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
static struct inode *__lookup_inode(struct super_block *sb, u64 ino)
|
2009-10-06 12:31:13 -06:00
|
|
|
{
|
2011-04-06 10:31:40 -06:00
|
|
|
struct ceph_mds_client *mdsc = ceph_sb_to_client(sb)->mdsc;
|
2009-10-06 12:31:13 -06:00
|
|
|
struct inode *inode;
|
|
|
|
struct ceph_vino vino;
|
|
|
|
int err;
|
|
|
|
|
2014-03-01 03:05:41 -07:00
|
|
|
vino.ino = ino;
|
2009-10-06 12:31:13 -06:00
|
|
|
vino.snap = CEPH_NOSNAP;
|
|
|
|
inode = ceph_find_inode(sb, vino);
|
2011-04-06 10:31:40 -06:00
|
|
|
if (!inode) {
|
|
|
|
struct ceph_mds_request *req;
|
2016-03-06 19:34:50 -07:00
|
|
|
int mask;
|
2011-04-06 10:31:40 -06:00
|
|
|
|
|
|
|
req = ceph_mdsc_create_request(mdsc, CEPH_MDS_OP_LOOKUPINO,
|
|
|
|
USE_ANY_MDS);
|
|
|
|
if (IS_ERR(req))
|
|
|
|
return ERR_CAST(req);
|
|
|
|
|
2016-03-06 19:34:50 -07:00
|
|
|
mask = CEPH_STAT_CAP_INODE;
|
|
|
|
if (ceph_security_xattr_wanted(d_inode(sb->s_root)))
|
|
|
|
mask |= CEPH_CAP_XATTR_SHARED;
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
req->r_args.lookupino.mask = cpu_to_le32(mask);
|
2016-03-06 19:34:50 -07:00
|
|
|
|
2011-04-06 10:31:40 -06:00
|
|
|
req->r_ino1 = vino;
|
|
|
|
req->r_num_caps = 1;
|
|
|
|
err = ceph_mdsc_do_request(mdsc, NULL, req);
|
2011-04-06 10:35:00 -06:00
|
|
|
inode = req->r_target_inode;
|
|
|
|
if (inode)
|
2011-05-27 10:24:26 -06:00
|
|
|
ihold(inode);
|
2011-04-06 10:31:40 -06:00
|
|
|
ceph_mdsc_put_request(req);
|
|
|
|
if (!inode)
|
2019-03-21 04:20:09 -06:00
|
|
|
return err < 0 ? ERR_PTR(err) : ERR_PTR(-ESTALE);
|
2011-04-06 10:31:40 -06:00
|
|
|
}
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
return inode;
|
|
|
|
}
|
2009-10-06 12:31:13 -06:00
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
struct inode *ceph_lookup_inode(struct super_block *sb, u64 ino)
|
|
|
|
{
|
|
|
|
struct inode *inode = __lookup_inode(sb, ino);
|
|
|
|
if (IS_ERR(inode))
|
|
|
|
return inode;
|
|
|
|
if (inode->i_nlink == 0) {
|
|
|
|
iput(inode);
|
|
|
|
return ERR_PTR(-ESTALE);
|
|
|
|
}
|
2019-03-21 04:20:09 -06:00
|
|
|
return inode;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct dentry *__fh_to_dentry(struct super_block *sb, u64 ino)
|
|
|
|
{
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
struct inode *inode = __lookup_inode(sb, ino);
|
2019-03-21 04:20:09 -06:00
|
|
|
if (IS_ERR(inode))
|
|
|
|
return ERR_CAST(inode);
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
if (inode->i_nlink == 0) {
|
|
|
|
iput(inode);
|
|
|
|
return ERR_PTR(-ESTALE);
|
|
|
|
}
|
2016-10-28 20:05:13 -06:00
|
|
|
return d_obtain_alias(inode);
|
2009-10-06 12:31:13 -06:00
|
|
|
}
|
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
static struct dentry *__snapfh_to_dentry(struct super_block *sb,
|
|
|
|
struct ceph_nfs_snapfh *sfh,
|
|
|
|
bool want_parent)
|
|
|
|
{
|
|
|
|
struct ceph_mds_client *mdsc = ceph_sb_to_client(sb)->mdsc;
|
|
|
|
struct ceph_mds_request *req;
|
|
|
|
struct inode *inode;
|
|
|
|
struct ceph_vino vino;
|
|
|
|
int mask;
|
|
|
|
int err;
|
|
|
|
bool unlinked = false;
|
|
|
|
|
|
|
|
if (want_parent) {
|
|
|
|
vino.ino = sfh->parent_ino;
|
|
|
|
if (sfh->snapid == CEPH_SNAPDIR)
|
|
|
|
vino.snap = CEPH_NOSNAP;
|
|
|
|
else if (sfh->ino == sfh->parent_ino)
|
|
|
|
vino.snap = CEPH_SNAPDIR;
|
|
|
|
else
|
|
|
|
vino.snap = sfh->snapid;
|
|
|
|
} else {
|
|
|
|
vino.ino = sfh->ino;
|
|
|
|
vino.snap = sfh->snapid;
|
|
|
|
}
|
|
|
|
inode = ceph_find_inode(sb, vino);
|
|
|
|
if (inode)
|
|
|
|
return d_obtain_alias(inode);
|
|
|
|
|
|
|
|
req = ceph_mdsc_create_request(mdsc, CEPH_MDS_OP_LOOKUPINO,
|
|
|
|
USE_ANY_MDS);
|
|
|
|
if (IS_ERR(req))
|
|
|
|
return ERR_CAST(req);
|
|
|
|
|
|
|
|
mask = CEPH_STAT_CAP_INODE;
|
|
|
|
if (ceph_security_xattr_wanted(d_inode(sb->s_root)))
|
|
|
|
mask |= CEPH_CAP_XATTR_SHARED;
|
|
|
|
req->r_args.lookupino.mask = cpu_to_le32(mask);
|
|
|
|
if (vino.snap < CEPH_NOSNAP) {
|
|
|
|
req->r_args.lookupino.snapid = cpu_to_le64(vino.snap);
|
|
|
|
if (!want_parent && sfh->ino != sfh->parent_ino) {
|
|
|
|
req->r_args.lookupino.parent =
|
|
|
|
cpu_to_le64(sfh->parent_ino);
|
|
|
|
req->r_args.lookupino.hash =
|
|
|
|
cpu_to_le32(sfh->hash);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
req->r_ino1 = vino;
|
|
|
|
req->r_num_caps = 1;
|
|
|
|
err = ceph_mdsc_do_request(mdsc, NULL, req);
|
|
|
|
inode = req->r_target_inode;
|
|
|
|
if (inode) {
|
|
|
|
if (vino.snap == CEPH_SNAPDIR) {
|
|
|
|
if (inode->i_nlink == 0)
|
|
|
|
unlinked = true;
|
|
|
|
inode = ceph_get_snapdir(inode);
|
|
|
|
} else if (ceph_snap(inode) == vino.snap) {
|
|
|
|
ihold(inode);
|
|
|
|
} else {
|
|
|
|
/* mds does not support lookup snapped inode */
|
|
|
|
err = -EOPNOTSUPP;
|
|
|
|
inode = NULL;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
ceph_mdsc_put_request(req);
|
|
|
|
|
|
|
|
if (want_parent) {
|
|
|
|
dout("snapfh_to_parent %llx.%llx\n err=%d\n",
|
|
|
|
vino.ino, vino.snap, err);
|
|
|
|
} else {
|
|
|
|
dout("snapfh_to_dentry %llx.%llx parent %llx hash %x err=%d",
|
|
|
|
vino.ino, vino.snap, sfh->parent_ino, sfh->hash, err);
|
|
|
|
}
|
|
|
|
if (!inode)
|
|
|
|
return ERR_PTR(-ESTALE);
|
|
|
|
/* see comments in ceph_get_parent() */
|
|
|
|
return unlinked ? d_obtain_root(inode) : d_obtain_alias(inode);
|
|
|
|
}
|
|
|
|
|
2009-10-06 12:31:13 -06:00
|
|
|
/*
|
2014-03-01 03:05:41 -07:00
|
|
|
* convert regular fh to dentry
|
2009-10-06 12:31:13 -06:00
|
|
|
*/
|
2014-03-01 03:05:41 -07:00
|
|
|
static struct dentry *ceph_fh_to_dentry(struct super_block *sb,
|
|
|
|
struct fid *fid,
|
|
|
|
int fh_len, int fh_type)
|
2009-10-06 12:31:13 -06:00
|
|
|
{
|
2014-03-01 03:05:41 -07:00
|
|
|
struct ceph_nfs_fh *fh = (void *)fid->raw;
|
2009-10-06 12:31:13 -06:00
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
if (fh_type == FILEID_BTRFS_WITH_PARENT) {
|
|
|
|
struct ceph_nfs_snapfh *sfh = (void *)fid->raw;
|
|
|
|
return __snapfh_to_dentry(sb, sfh, false);
|
|
|
|
}
|
|
|
|
|
2014-03-01 03:05:41 -07:00
|
|
|
if (fh_type != FILEID_INO32_GEN &&
|
|
|
|
fh_type != FILEID_INO32_GEN_PARENT)
|
|
|
|
return NULL;
|
|
|
|
if (fh_len < sizeof(*fh) / 4)
|
|
|
|
return NULL;
|
2009-10-06 12:31:13 -06:00
|
|
|
|
2014-03-01 03:05:41 -07:00
|
|
|
dout("fh_to_dentry %llx\n", fh->ino);
|
|
|
|
return __fh_to_dentry(sb, fh->ino);
|
2009-10-06 12:31:13 -06:00
|
|
|
}
|
|
|
|
|
2014-03-01 07:11:45 -07:00
|
|
|
static struct dentry *__get_parent(struct super_block *sb,
|
|
|
|
struct dentry *child, u64 ino)
|
|
|
|
{
|
|
|
|
struct ceph_mds_client *mdsc = ceph_sb_to_client(sb)->mdsc;
|
|
|
|
struct ceph_mds_request *req;
|
|
|
|
struct inode *inode;
|
2016-03-06 19:34:50 -07:00
|
|
|
int mask;
|
2014-03-01 07:11:45 -07:00
|
|
|
int err;
|
|
|
|
|
|
|
|
req = ceph_mdsc_create_request(mdsc, CEPH_MDS_OP_LOOKUPPARENT,
|
|
|
|
USE_ANY_MDS);
|
|
|
|
if (IS_ERR(req))
|
|
|
|
return ERR_CAST(req);
|
|
|
|
|
|
|
|
if (child) {
|
2015-03-17 16:25:59 -06:00
|
|
|
req->r_inode = d_inode(child);
|
|
|
|
ihold(d_inode(child));
|
2014-03-01 07:11:45 -07:00
|
|
|
} else {
|
|
|
|
req->r_ino1 = (struct ceph_vino) {
|
|
|
|
.ino = ino,
|
|
|
|
.snap = CEPH_NOSNAP,
|
|
|
|
};
|
|
|
|
}
|
2016-03-06 19:34:50 -07:00
|
|
|
|
|
|
|
mask = CEPH_STAT_CAP_INODE;
|
|
|
|
if (ceph_security_xattr_wanted(d_inode(sb->s_root)))
|
|
|
|
mask |= CEPH_CAP_XATTR_SHARED;
|
|
|
|
req->r_args.getattr.mask = cpu_to_le32(mask);
|
|
|
|
|
2014-03-01 07:11:45 -07:00
|
|
|
req->r_num_caps = 1;
|
|
|
|
err = ceph_mdsc_do_request(mdsc, NULL, req);
|
|
|
|
inode = req->r_target_inode;
|
|
|
|
if (inode)
|
|
|
|
ihold(inode);
|
|
|
|
ceph_mdsc_put_request(req);
|
|
|
|
if (!inode)
|
|
|
|
return ERR_PTR(-ENOENT);
|
|
|
|
|
2016-10-28 20:05:13 -06:00
|
|
|
return d_obtain_alias(inode);
|
2014-03-01 07:11:45 -07:00
|
|
|
}
|
|
|
|
|
2014-04-09 00:11:31 -06:00
|
|
|
static struct dentry *ceph_get_parent(struct dentry *child)
|
2014-03-01 07:11:45 -07:00
|
|
|
{
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
struct inode *inode = d_inode(child);
|
|
|
|
struct dentry *dn;
|
|
|
|
|
|
|
|
if (ceph_snap(inode) != CEPH_NOSNAP) {
|
|
|
|
struct inode* dir;
|
|
|
|
bool unlinked = false;
|
|
|
|
/* do not support non-directory */
|
|
|
|
if (!d_is_dir(child)) {
|
|
|
|
dn = ERR_PTR(-EINVAL);
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
dir = __lookup_inode(inode->i_sb, ceph_ino(inode));
|
|
|
|
if (IS_ERR(dir)) {
|
|
|
|
dn = ERR_CAST(dir);
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
/* There can be multiple paths to access snapped inode.
|
|
|
|
* For simplicity, treat snapdir of head inode as parent */
|
|
|
|
if (ceph_snap(inode) != CEPH_SNAPDIR) {
|
|
|
|
struct inode *snapdir = ceph_get_snapdir(dir);
|
|
|
|
if (dir->i_nlink == 0)
|
|
|
|
unlinked = true;
|
|
|
|
iput(dir);
|
|
|
|
if (IS_ERR(snapdir)) {
|
|
|
|
dn = ERR_CAST(snapdir);
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
dir = snapdir;
|
|
|
|
}
|
|
|
|
/* If directory has already been deleted, futher get_parent
|
|
|
|
* will fail. Do not mark snapdir dentry as disconnected,
|
|
|
|
* this prevent exportfs from doing futher get_parent. */
|
|
|
|
if (unlinked)
|
|
|
|
dn = d_obtain_root(dir);
|
|
|
|
else
|
|
|
|
dn = d_obtain_alias(dir);
|
|
|
|
} else {
|
|
|
|
dn = __get_parent(child->d_sb, child, 0);
|
|
|
|
}
|
|
|
|
out:
|
|
|
|
dout("get_parent %p ino %llx.%llx err=%ld\n",
|
2019-05-25 03:15:59 -06:00
|
|
|
child, ceph_vinop(inode), (long)PTR_ERR_OR_ZERO(dn));
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
return dn;
|
2014-03-01 07:11:45 -07:00
|
|
|
}
|
|
|
|
|
2009-10-06 12:31:13 -06:00
|
|
|
/*
|
2014-03-01 08:09:05 -07:00
|
|
|
* convert regular fh to parent
|
2009-10-06 12:31:13 -06:00
|
|
|
*/
|
|
|
|
static struct dentry *ceph_fh_to_parent(struct super_block *sb,
|
2014-03-01 08:09:05 -07:00
|
|
|
struct fid *fid,
|
2009-10-06 12:31:13 -06:00
|
|
|
int fh_len, int fh_type)
|
|
|
|
{
|
|
|
|
struct ceph_nfs_confh *cfh = (void *)fid->raw;
|
|
|
|
struct dentry *dentry;
|
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
if (fh_type == FILEID_BTRFS_WITH_PARENT) {
|
|
|
|
struct ceph_nfs_snapfh *sfh = (void *)fid->raw;
|
|
|
|
return __snapfh_to_dentry(sb, sfh, true);
|
|
|
|
}
|
|
|
|
|
2014-03-01 08:09:05 -07:00
|
|
|
if (fh_type != FILEID_INO32_GEN_PARENT)
|
|
|
|
return NULL;
|
tmpfs,ceph,gfs2,isofs,reiserfs,xfs: fix fh_len checking
Fuzzing with trinity oopsed on the 1st instruction of shmem_fh_to_dentry(),
u64 inum = fid->raw[2];
which is unhelpfully reported as at the end of shmem_alloc_inode():
BUG: unable to handle kernel paging request at ffff880061cd3000
IP: [<ffffffff812190d0>] shmem_alloc_inode+0x40/0x40
Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
Call Trace:
[<ffffffff81488649>] ? exportfs_decode_fh+0x79/0x2d0
[<ffffffff812d77c3>] do_handle_open+0x163/0x2c0
[<ffffffff812d792c>] sys_open_by_handle_at+0xc/0x10
[<ffffffff83a5f3f8>] tracesys+0xe1/0xe6
Right, tmpfs is being stupid to access fid->raw[2] before validating that
fh_len includes it: the buffer kmalloc'ed by do_sys_name_to_handle() may
fall at the end of a page, and the next page not be present.
But some other filesystems (ceph, gfs2, isofs, reiserfs, xfs) are being
careless about fh_len too, in fh_to_dentry() and/or fh_to_parent(), and
could oops in the same way: add the missing fh_len checks to those.
Reported-by: Sasha Levin <levinsasha928@gmail.com>
Signed-off-by: Hugh Dickins <hughd@google.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Sage Weil <sage@inktank.com>
Cc: Steven Whitehouse <swhiteho@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2012-10-07 21:32:51 -06:00
|
|
|
if (fh_len < sizeof(*cfh) / 4)
|
2014-03-01 08:09:05 -07:00
|
|
|
return NULL;
|
2009-10-06 12:31:13 -06:00
|
|
|
|
2014-03-01 08:09:05 -07:00
|
|
|
dout("fh_to_parent %llx\n", cfh->parent_ino);
|
|
|
|
dentry = __get_parent(sb, NULL, cfh->ino);
|
2016-06-24 21:49:03 -06:00
|
|
|
if (unlikely(dentry == ERR_PTR(-ENOENT)))
|
2014-03-01 08:09:05 -07:00
|
|
|
dentry = __fh_to_dentry(sb, cfh->parent_ino);
|
2009-10-06 12:31:13 -06:00
|
|
|
return dentry;
|
|
|
|
}
|
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
static int __get_snap_name(struct dentry *parent, char *name,
|
|
|
|
struct dentry *child)
|
|
|
|
{
|
|
|
|
struct inode *inode = d_inode(child);
|
|
|
|
struct inode *dir = d_inode(parent);
|
|
|
|
struct ceph_fs_client *fsc = ceph_inode_to_client(inode);
|
|
|
|
struct ceph_mds_request *req = NULL;
|
|
|
|
char *last_name = NULL;
|
|
|
|
unsigned next_offset = 2;
|
|
|
|
int err = -EINVAL;
|
|
|
|
|
|
|
|
if (ceph_ino(inode) != ceph_ino(dir))
|
|
|
|
goto out;
|
|
|
|
if (ceph_snap(inode) == CEPH_SNAPDIR) {
|
|
|
|
if (ceph_snap(dir) == CEPH_NOSNAP) {
|
|
|
|
strcpy(name, fsc->mount_options->snapdir_name);
|
|
|
|
err = 0;
|
|
|
|
}
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
if (ceph_snap(dir) != CEPH_SNAPDIR)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
while (1) {
|
|
|
|
struct ceph_mds_reply_info_parsed *rinfo;
|
|
|
|
struct ceph_mds_reply_dir_entry *rde;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
req = ceph_mdsc_create_request(fsc->mdsc, CEPH_MDS_OP_LSSNAP,
|
|
|
|
USE_AUTH_MDS);
|
|
|
|
if (IS_ERR(req)) {
|
|
|
|
err = PTR_ERR(req);
|
|
|
|
req = NULL;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
err = ceph_alloc_readdir_reply_buffer(req, inode);
|
|
|
|
if (err)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
req->r_direct_mode = USE_AUTH_MDS;
|
|
|
|
req->r_readdir_offset = next_offset;
|
|
|
|
req->r_args.readdir.flags =
|
|
|
|
cpu_to_le16(CEPH_READDIR_REPLY_BITFLAGS);
|
|
|
|
if (last_name) {
|
|
|
|
req->r_path2 = last_name;
|
|
|
|
last_name = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
req->r_inode = dir;
|
|
|
|
ihold(dir);
|
|
|
|
req->r_dentry = dget(parent);
|
|
|
|
|
|
|
|
inode_lock(dir);
|
|
|
|
err = ceph_mdsc_do_request(fsc->mdsc, NULL, req);
|
|
|
|
inode_unlock(dir);
|
|
|
|
|
|
|
|
if (err < 0)
|
|
|
|
goto out;
|
|
|
|
|
|
|
|
rinfo = &req->r_reply_info;
|
|
|
|
for (i = 0; i < rinfo->dir_nr; i++) {
|
|
|
|
rde = rinfo->dir_entries + i;
|
|
|
|
BUG_ON(!rde->inode.in);
|
|
|
|
if (ceph_snap(inode) ==
|
|
|
|
le64_to_cpu(rde->inode.in->snapid)) {
|
|
|
|
memcpy(name, rde->name, rde->name_len);
|
|
|
|
name[rde->name_len] = '\0';
|
|
|
|
err = 0;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (rinfo->dir_end)
|
|
|
|
break;
|
|
|
|
|
|
|
|
BUG_ON(rinfo->dir_nr <= 0);
|
|
|
|
rde = rinfo->dir_entries + (rinfo->dir_nr - 1);
|
|
|
|
next_offset += rinfo->dir_nr;
|
|
|
|
last_name = kstrndup(rde->name, rde->name_len, GFP_KERNEL);
|
|
|
|
if (!last_name) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
ceph_mdsc_put_request(req);
|
|
|
|
req = NULL;
|
|
|
|
}
|
|
|
|
err = -ENOENT;
|
|
|
|
out:
|
|
|
|
if (req)
|
|
|
|
ceph_mdsc_put_request(req);
|
|
|
|
kfree(last_name);
|
|
|
|
dout("get_snap_name %p ino %llx.%llx err=%d\n",
|
|
|
|
child, ceph_vinop(inode), err);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2014-03-06 01:40:32 -07:00
|
|
|
static int ceph_get_name(struct dentry *parent, char *name,
|
|
|
|
struct dentry *child)
|
|
|
|
{
|
|
|
|
struct ceph_mds_client *mdsc;
|
|
|
|
struct ceph_mds_request *req;
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
struct inode *inode = d_inode(child);
|
2014-03-06 01:40:32 -07:00
|
|
|
int err;
|
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
if (ceph_snap(inode) != CEPH_NOSNAP)
|
|
|
|
return __get_snap_name(parent, name, child);
|
|
|
|
|
|
|
|
mdsc = ceph_inode_to_client(inode)->mdsc;
|
2014-03-06 01:40:32 -07:00
|
|
|
req = ceph_mdsc_create_request(mdsc, CEPH_MDS_OP_LOOKUPNAME,
|
|
|
|
USE_ANY_MDS);
|
|
|
|
if (IS_ERR(req))
|
|
|
|
return PTR_ERR(req);
|
|
|
|
|
2016-01-22 13:40:57 -07:00
|
|
|
inode_lock(d_inode(parent));
|
2014-03-06 01:40:32 -07:00
|
|
|
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
req->r_inode = inode;
|
|
|
|
ihold(inode);
|
2015-03-17 16:25:59 -06:00
|
|
|
req->r_ino2 = ceph_vino(d_inode(parent));
|
2017-01-31 08:28:26 -07:00
|
|
|
req->r_parent = d_inode(parent);
|
|
|
|
set_bit(CEPH_MDS_R_PARENT_LOCKED, &req->r_req_flags);
|
2014-03-06 01:40:32 -07:00
|
|
|
req->r_num_caps = 2;
|
|
|
|
err = ceph_mdsc_do_request(mdsc, NULL, req);
|
|
|
|
|
2016-01-22 13:40:57 -07:00
|
|
|
inode_unlock(d_inode(parent));
|
2014-03-06 01:40:32 -07:00
|
|
|
|
|
|
|
if (!err) {
|
|
|
|
struct ceph_mds_reply_info_parsed *rinfo = &req->r_reply_info;
|
|
|
|
memcpy(name, rinfo->dname, rinfo->dname_len);
|
|
|
|
name[rinfo->dname_len] = 0;
|
|
|
|
dout("get_name %p ino %llx.%llx name %s\n",
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
child, ceph_vinop(inode), name);
|
2014-03-06 01:40:32 -07:00
|
|
|
} else {
|
|
|
|
dout("get_name %p ino %llx.%llx err %d\n",
|
ceph: snapshot nfs re-export
To support snapshot nfs re-export, we need a way to lookup snapped
inode by file handle. For directory inode, snapped metadata are always
stored together with head inode. Client just need to pass vinodeno_t
to MDS. For non-directory inode, there can be multiple version of
snapped inodes and they can be stored in different dirfrags. Besides
vinodeno_t, client also need to tell mds from which dirfrag it got the
snapped inode.
Another problem of supporting snapshot nfs re-export is that there
can be multiple paths to access a snapped inode. For example:
mkdir -p d1/d2/d3
mkdir d1/.snap/s1
Paths 'd1/.snap/s1/d2/d3', 'd1/d2/.snap/_s1_<inode number of d1>/d3'
and 'd1/d2/d3/.snap/_s1_<inode number of d1>' are all reference to the
same snapped inode. For a given snapped inode, There is no convenient
way to get the first form and the second form paths. For simplicity,
ceph_get_parent() return snapdir for snapped directory inode.
Furthermore, client may access snapshot of deleted directory. For
example:
mkdir -p d1/d2
mkdir d1/.snap/s1
open d1/.snap/s1/d2
rm -rf d1/d2
<nfs server restart>
The path constucted by ceph_get_parent() and ceph_get_name() is
'<inode of d2>/.snap/_s1_<inode number of d1>'. Futher lookup parent
of <inode of d2> will fail. To workaround this case, this patch uses
d_obtain_root() to get dentry for snapdir of deleted directory.
snapdir dentry has no DCACHE_DISCONNECTED flag set, reconnect_path()
stops when it reaches snapdir dentry.
Link: http://tracker.ceph.com/issues/22105
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2017-11-15 02:39:40 -07:00
|
|
|
child, ceph_vinop(inode), err);
|
2014-03-06 01:40:32 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
ceph_mdsc_put_request(req);
|
|
|
|
return err;
|
|
|
|
}
|
|
|
|
|
2009-10-06 12:31:13 -06:00
|
|
|
const struct export_operations ceph_export_ops = {
|
|
|
|
.encode_fh = ceph_encode_fh,
|
|
|
|
.fh_to_dentry = ceph_fh_to_dentry,
|
|
|
|
.fh_to_parent = ceph_fh_to_parent,
|
2014-03-01 07:11:45 -07:00
|
|
|
.get_parent = ceph_get_parent,
|
2014-03-06 01:40:32 -07:00
|
|
|
.get_name = ceph_get_name,
|
2009-10-06 12:31:13 -06:00
|
|
|
};
|