user/sven/linux.git/include/linux/file.h, branch v3.9

switch simple cases of fget_light to fdget

2012-09-27T02:20:08Z

Signed-off-by: Al Viro

new helpers: fdget()/fdput()

2012-09-27T01:16:32Z

Signed-off-bs: Al Viro

make expand_files() and alloc_fd() static

2012-09-27T01:09:58Z

no callers outside of fs/file.c left Signed-off-by: Al Viro

new helper: replace_fd()

2012-09-27T01:09:57Z

analog of dup2(), except that it takes struct file * as source. Signed-off-by: Al Viro

take purely descriptor-related stuff from fcntl.c to file.c

2012-09-27T01:09:57Z

Signed-off-by: Al Viro

make get_unused_fd_flags() a function

2012-09-27T01:08:50Z

... and get_unused_fd() a macro around it Signed-off-by: Al Viro

switch fput to task_work_add

2012-07-22T19:57:58Z

... and schedule_work() for interrupt/kernel_thread callers (and yes, now it *is* OK to call from interrupt). We are guaranteed that __fput() will be done before we return to userland (or exit). Note that for fput() from a kernel thread we get an async behaviour; it's almost always OK, but sometimes you might need to have __fput() completed before you do anything else. There are two mechanisms for that - a general barrier (flush_delayed_fput()) and explicit __fput_sync(). Both should be used with care (as was the case for fput() from kernel threads all along). See comments in fs/file_table.c for details. Signed-off-by: Al Viro

vfs: drop_file_write_access() made static

2012-03-21T01:29:32Z

Signed-off-by: Al Viro

New kind of open files - "location only".

2011-03-15T06:21:45Z

New flag for open(2) - O_PATH. Semantics: * pathname is resolved, but the file itself is _NOT_ opened as far as filesystem is concerned. * almost all operations on the resulting descriptors shall fail with -EBADF. Exceptions are: 1) operations on descriptors themselves (i.e. close(), dup(), dup2(), dup3(), fcntl(fd, F_DUPFD), fcntl(fd, F_DUPFD_CLOEXEC, ...), fcntl(fd, F_GETFD), fcntl(fd, F_SETFD, ...)) 2) fcntl(fd, F_GETFL), for a common non-destructive way to check if descriptor is open 3) "dfd" arguments of ...at(2) syscalls, i.e. the starting points of pathname resolution * closing such descriptor does *NOT* affect dnotify or posix locks. * permissions are checked as usual along the way to file; no permission checks are applied to the file itself. Of course, giving such thing to syscall will result in permission checks (at the moment it means checking that starting point of ....at() is a directory and caller has exec permissions on it). fget() and fget_light() return NULL on such descriptors; use of fget_raw() and fget_raw_light() is needed to get them. That protects existing code from dealing with those things. There are two things still missing (they come in the next commits): one is handling of symlinks (right now we refuse to open them that way; see the next commit for semantics related to those) and another is descriptor passing via SCM_RIGHTS datagrams. Signed-off-by: Al Viro

fs: Remove unlikely() from fput_light()

2011-01-17T08:26:26Z

In fput_light(), there's an unlikely(fput_needed), which running on my normal desktop doing firefox, xchat, evolution and part of my distcc farm, and running the annotate branch profiler shows that the unlikely is not very unlikely. correct incorrect % Function File Line ------- --------- - -------- ---- ---- 0 48 100 fput_light file.h 26 115828710 897415279 88 fput_light file.h 26 865271179 5286128445 85 fput_light file.h 26 19568539 8923664 31 fput_light file.h 26 12353677 3562279 22 fput_light file.h 26 267691 67062 20 fput_light file.h 26 15014853 348172 2 fput_light file.h 26 209258 205 0 fput_light file.h 26 1364164 0 0 fput_light file.h 26 Which gives 1032903812 times it was correct and 6203351846 times it was incorrect, or 85% incorrect. Cc: Andrew Morton Signed-off-by: Steven Rostedt Signed-off-by: Al Viro