linux.git/include/linux/namei.h, branch v3.1-rc3

switch vfs_path_lookup() to struct path

2011-07-20T05:44:14+00:00

Signed-off-by: Al Viro

new helpers: kern_path_create/user_path_create

2011-07-20T05:44:05+00:00

combination of kern_path_parent() and lookup_create().  Does *not*
expose struct nameidata to caller.  Syscalls converted to that...

Signed-off-by: Al Viro

kill LOOKUP_CONTINUE

2011-07-20T05:44:03+00:00

LOOKUP_PARENT is equivalent to it now

Signed-off-by: Al Viro

don't pass 'mounting_here' flag to follow_down()

2011-03-18T13:04:20+00:00

it's always false now

Signed-off-by: Al Viro

New AT_... flag: AT_EMPTY_PATH

2011-03-14T23:12:20+00:00

For name_to_handle_at(2) we'll want both ...at()-style syscall that
would be usable for non-directory descriptors (with empty relative
pathname).  Introduce new flag (AT_EMPTY_PATH) to deal with that and
corresponding LOOKUP_EMPTY; teach user_path_at() and path_init() to
deal with the latter.

Signed-off-by: Al Viro

reduce vfs_path_lookup() to do_path_lookup()

2011-03-14T13:15:27+00:00

New lookup flag: LOOKUP_ROOT.  nd->root is set (and held) by caller,
path_init() starts walking from that place and all pathname resolution
machinery never drops nd->root if that flag is set.  That turns
vfs_path_lookup() into a special case of do_path_lookup() *and*
gets us down to 3 callers of link_path_walk(), making it finally
feasible to rip the handling of trailing symlink out of link_path_walk().
That will not only simply the living hell out of it, but make life
much simpler for unionfs merge.  Trailing symlink handling will
become iterative, which is a good thing for stack footprint in
a lot of situations as well.

Signed-off-by: Al Viro

get rid of nd->file

2011-03-14T13:15:26+00:00

Don't stash the struct file * used as starting point of walk in nameidata;
pass file ** to path_init() instead.

Signed-off-by: Al Viro

untangle the "need_reval_dot" mess

2011-03-14T13:15:24+00:00

instead of ad-hackery around need_reval_dot(), do the following:
set a flag (LOOKUP_JUMPED) in the beginning of path, on absolute
symlink traversal, on ".." and on procfs-style symlinks.  Clear on
normal components, leave unchanged on ".".  Non-nested callers of
link_path_walk() call handle_reval_path(), which checks that flag
is set and that fs does want the final revalidate thing, then does
->d_revalidate().  In link_path_walk() all the return_reval stuff
is gone.

Signed-off-by: Al Viro

kill path_lookup()

2011-03-14T13:15:23+00:00

all remaining callers pass LOOKUP_PARENT to it, so
flags argument can die; renamed to kern_path_parent()

Signed-off-by: Al Viro

Add an AT_NO_AUTOMOUNT flag to suppress terminal automount

2011-01-16T01:07:33+00:00

Add an AT_NO_AUTOMOUNT flag to suppress terminal automounting of automount
point directories.  This can be used by fstatat() users to permit the
gathering of attributes on an automount point and also prevent
mass-automounting of a directory of automount points by ls.

Signed-off-by: David Howells 
Acked-by: Ian Kent 
Signed-off-by: Al Viro