2019-05-27 08:55:05 +02:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
2021-03-30 17:44:48 +01:00
|
|
|
/*
|
2006-10-04 02:16:22 -07:00
|
|
|
* eCryptfs: Linux filesystem encryption layer
|
|
|
|
*
|
|
|
|
* Copyright (C) 1997-2003 Erez Zadok
|
|
|
|
* Copyright (C) 2001-2003 Stony Brook University
|
|
|
|
* Copyright (C) 2004-2006 International Business Machines Corp.
|
|
|
|
* Author(s): Michael A. Halcrow <mahalcro@us.ibm.com>
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/dcache.h>
|
|
|
|
#include <linux/namei.h>
|
2006-10-30 22:07:20 -08:00
|
|
|
#include <linux/mount.h>
|
2006-12-08 02:36:31 -08:00
|
|
|
#include <linux/fs_stack.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 17:04:11 +09:00
|
|
|
#include <linux/slab.h>
|
2006-10-04 02:16:22 -07:00
|
|
|
#include "ecryptfs_kernel.h"
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ecryptfs_d_revalidate - revalidate an ecryptfs dentry
|
Pass parent directory inode and expected name to ->d_revalidate()
->d_revalidate() often needs to access dentry parent and name; that has
to be done carefully, since the locking environment varies from caller
to caller. We are not guaranteed that dentry in question will not be
moved right under us - not unless the filesystem is such that nothing
on it ever gets renamed.
It can be dealt with, but that results in boilerplate code that isn't
even needed - the callers normally have just found the dentry via dcache
lookup and want to verify that it's in the right place; they already
have the values of ->d_parent and ->d_name stable. There is a couple
of exceptions (overlayfs and, to less extent, ecryptfs), but for the
majority of calls that song and dance is not needed at all.
It's easier to make ecryptfs and overlayfs find and pass those values if
there's a ->d_revalidate() instance to be called, rather than doing that
in the instances.
This commit only changes the calling conventions; making use of supplied
values is left to followups.
NOTE: some instances need more than just the parent - things like CIFS
may need to build an entire path from filesystem root, so they need
more precautions than the usual boilerplate. This series doesn't
do anything to that need - these filesystems have to keep their locking
mechanisms (rename_lock loops, use of dentry_path_raw(), private rwsem
a-la v9fs).
One thing to keep in mind when using name is that name->name will normally
point into the pathname being resolved; the filename in question occupies
name->len bytes starting at name->name, and there is NUL somewhere after it,
but it the next byte might very well be '/' rather than '\0'. Do not
ignore name->len.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Gabriel Krisman Bertazi <gabriel@krisman.be>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2024-12-08 00:28:51 -05:00
|
|
|
* @dir: inode of expected parent
|
|
|
|
* @name: expected name
|
|
|
|
* @dentry: dentry to revalidate
|
2012-06-10 16:03:43 -04:00
|
|
|
* @flags: lookup flags
|
2006-10-04 02:16:22 -07:00
|
|
|
*
|
|
|
|
* Called when the VFS needs to revalidate a dentry. This
|
|
|
|
* is called whenever a name lookup finds a dentry in the
|
|
|
|
* dcache. Most filesystems leave this as NULL, because all their
|
|
|
|
* dentries in the dcache are valid.
|
|
|
|
*
|
|
|
|
* Returns 1 if valid, 0 otherwise.
|
|
|
|
*
|
|
|
|
*/
|
Pass parent directory inode and expected name to ->d_revalidate()
->d_revalidate() often needs to access dentry parent and name; that has
to be done carefully, since the locking environment varies from caller
to caller. We are not guaranteed that dentry in question will not be
moved right under us - not unless the filesystem is such that nothing
on it ever gets renamed.
It can be dealt with, but that results in boilerplate code that isn't
even needed - the callers normally have just found the dentry via dcache
lookup and want to verify that it's in the right place; they already
have the values of ->d_parent and ->d_name stable. There is a couple
of exceptions (overlayfs and, to less extent, ecryptfs), but for the
majority of calls that song and dance is not needed at all.
It's easier to make ecryptfs and overlayfs find and pass those values if
there's a ->d_revalidate() instance to be called, rather than doing that
in the instances.
This commit only changes the calling conventions; making use of supplied
values is left to followups.
NOTE: some instances need more than just the parent - things like CIFS
may need to build an entire path from filesystem root, so they need
more precautions than the usual boilerplate. This series doesn't
do anything to that need - these filesystems have to keep their locking
mechanisms (rename_lock loops, use of dentry_path_raw(), private rwsem
a-la v9fs).
One thing to keep in mind when using name is that name->name will normally
point into the pathname being resolved; the filename in question occupies
name->len bytes starting at name->name, and there is NUL somewhere after it,
but it the next byte might very well be '/' rather than '\0'. Do not
ignore name->len.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Gabriel Krisman Bertazi <gabriel@krisman.be>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2024-12-08 00:28:51 -05:00
|
|
|
static int ecryptfs_d_revalidate(struct inode *dir, const struct qstr *name,
|
|
|
|
struct dentry *dentry, unsigned int flags)
|
2006-10-04 02:16:22 -07:00
|
|
|
{
|
2013-09-15 20:45:11 -04:00
|
|
|
struct dentry *lower_dentry = ecryptfs_dentry_to_lower(dentry);
|
2015-08-05 11:26:36 -05:00
|
|
|
int rc = 1;
|
2006-10-04 02:16:22 -07:00
|
|
|
|
2012-06-10 16:03:43 -04:00
|
|
|
if (flags & LOOKUP_RCU)
|
2011-01-07 17:49:57 +11:00
|
|
|
return -ECHILD;
|
|
|
|
|
Pass parent directory inode and expected name to ->d_revalidate()
->d_revalidate() often needs to access dentry parent and name; that has
to be done carefully, since the locking environment varies from caller
to caller. We are not guaranteed that dentry in question will not be
moved right under us - not unless the filesystem is such that nothing
on it ever gets renamed.
It can be dealt with, but that results in boilerplate code that isn't
even needed - the callers normally have just found the dentry via dcache
lookup and want to verify that it's in the right place; they already
have the values of ->d_parent and ->d_name stable. There is a couple
of exceptions (overlayfs and, to less extent, ecryptfs), but for the
majority of calls that song and dance is not needed at all.
It's easier to make ecryptfs and overlayfs find and pass those values if
there's a ->d_revalidate() instance to be called, rather than doing that
in the instances.
This commit only changes the calling conventions; making use of supplied
values is left to followups.
NOTE: some instances need more than just the parent - things like CIFS
may need to build an entire path from filesystem root, so they need
more precautions than the usual boilerplate. This series doesn't
do anything to that need - these filesystems have to keep their locking
mechanisms (rename_lock loops, use of dentry_path_raw(), private rwsem
a-la v9fs).
One thing to keep in mind when using name is that name->name will normally
point into the pathname being resolved; the filename in question occupies
name->len bytes starting at name->name, and there is NUL somewhere after it,
but it the next byte might very well be '/' rather than '\0'. Do not
ignore name->len.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Gabriel Krisman Bertazi <gabriel@krisman.be>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2024-12-08 00:28:51 -05:00
|
|
|
if (lower_dentry->d_flags & DCACHE_OP_REVALIDATE) {
|
|
|
|
struct inode *lower_dir = ecryptfs_inode_to_lower(dir);
|
|
|
|
struct name_snapshot n;
|
|
|
|
|
|
|
|
take_dentry_name_snapshot(&n, lower_dentry);
|
|
|
|
rc = lower_dentry->d_op->d_revalidate(lower_dir, &n.name,
|
|
|
|
lower_dentry, flags);
|
|
|
|
release_dentry_name_snapshot(&n);
|
|
|
|
}
|
2015-08-05 11:26:36 -05:00
|
|
|
|
2015-03-17 22:25:59 +00:00
|
|
|
if (d_really_is_positive(dentry)) {
|
2015-08-05 11:26:36 -05:00
|
|
|
struct inode *inode = d_inode(dentry);
|
2006-11-16 01:19:30 -08:00
|
|
|
|
2015-08-05 11:26:36 -05:00
|
|
|
fsstack_copy_attr_all(inode, ecryptfs_inode_to_lower(inode));
|
|
|
|
if (!inode->i_nlink)
|
|
|
|
return 0;
|
2006-11-16 01:19:30 -08:00
|
|
|
}
|
2006-10-04 02:16:22 -07:00
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
struct kmem_cache *ecryptfs_dentry_info_cache;
|
|
|
|
|
2013-09-15 20:45:11 -04:00
|
|
|
static void ecryptfs_dentry_free_rcu(struct rcu_head *head)
|
|
|
|
{
|
|
|
|
kmem_cache_free(ecryptfs_dentry_info_cache,
|
|
|
|
container_of(head, struct ecryptfs_dentry_info, rcu));
|
|
|
|
}
|
|
|
|
|
2006-10-04 02:16:22 -07:00
|
|
|
/**
|
|
|
|
* ecryptfs_d_release
|
|
|
|
* @dentry: The ecryptfs dentry
|
|
|
|
*
|
|
|
|
* Called when a dentry is really deallocated.
|
|
|
|
*/
|
|
|
|
static void ecryptfs_d_release(struct dentry *dentry)
|
|
|
|
{
|
2013-09-15 20:45:11 -04:00
|
|
|
struct ecryptfs_dentry_info *p = dentry->d_fsdata;
|
|
|
|
if (p) {
|
2013-09-15 20:54:18 -04:00
|
|
|
path_put(&p->lower_path);
|
2013-09-15 20:45:11 -04:00
|
|
|
call_rcu(&p->rcu, ecryptfs_dentry_free_rcu);
|
2006-10-30 22:07:20 -08:00
|
|
|
}
|
2006-10-04 02:16:22 -07:00
|
|
|
}
|
|
|
|
|
2009-02-20 05:57:52 +00:00
|
|
|
const struct dentry_operations ecryptfs_dops = {
|
2006-10-04 02:16:22 -07:00
|
|
|
.d_revalidate = ecryptfs_d_revalidate,
|
|
|
|
.d_release = ecryptfs_d_release,
|
|
|
|
};
|