linux.git/fs/internal.h, branch v3.7-rc2

vfs: make path_openat take a struct filename pointer

2012-10-13T00:15:09+00:00

...and fix up the callers. For do_file_open_root, just declare a
struct filename on the stack and fill out the .name field. For
do_filp_open, make it also take a struct filename pointer, and fix up its
callers to call it appropriately.

For filp_open, add a variant that takes a struct filename pointer and turn
filp_open into a wrapper around it.

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

fs: Add freezing handling to mnt_want_write() / mnt_drop_write()

2012-07-31T05:40:38+00:00

Most of places where we want freeze protection coincides with the places where
we also have remount-ro protection. So make mnt_want_write() and
mnt_drop_write() (and their _file alternative) prevent freezing as well.
For the few cases that are really interested only in remount-ro protection
provide new function variants.

BugLink: https://bugs.launchpad.net/bugs/897421
Tested-by: Kamal Mostafa 
Tested-by: Peter M. Petrakis 
Tested-by: Dann Frazier 
Tested-by: Massimo Morana 
Signed-off-by: Jan Kara 
Signed-off-by: Al Viro

VFS: Split inode_permission()

2012-07-14T12:38:36+00:00

Split inode_permission() into inode- and superblock-dependent parts.

This is aimed at unionmounts where the superblock from the upper layer has to
be checked rather than the superblock from the lower layer as the upper layer
may be writable, thus allowing an unwritable file from the lower layer to be
copied up and modified.

Original-author: Valerie Aurora 
Signed-off-by: David Howells  (Further development)
Signed-off-by: Al Viro

kill struct opendata

2012-07-14T12:33:39+00:00

Just pass struct file *.  Methods are happier that way...
There's no need to return struct file * from finish_open() now,
so let it return int.  Next: saner prototypes for parts in
namei.c

Signed-off-by: Al Viro

kill opendata->{mnt,dentry}

2012-07-14T12:33:37+00:00

->filp->f_path is there for purpose...

Signed-off-by: Al Viro

vfs: remove open intents from nameidata

2012-07-14T12:33:18+00:00

All users of open intents have been converted to use ->atomic_{open,create}.

This patch gets rid of nd->intent.open and related infrastructure.

Signed-off-by: Miklos Szeredi 
Signed-off-by: Al Viro

vfs: add i_op->atomic_open()

2012-07-14T12:33:04+00:00

Add a new inode operation which is called on the last component of an open.
Using this the filesystem can look up, possibly create and open the file in one
atomic operation.  If it cannot perform this (e.g. the file type turned out to
be wrong) it may signal this by returning NULL instead of an open struct file
pointer.

i_op->atomic_open() is only called if the last component is negative or needs
lookup.  Handling cached positive dentries here doesn't add much value: these
can be opened using f_op->open().  If the cached file turns out to be invalid,
the open can be retried, this time using ->atomic_open() with a fresh dentry.

For now leave the old way of using open intents in lookup and revalidate in
place.  This will be removed once all the users are converted.

David Howells noticed that if ->atomic_open() opens the file but does not create
it, handle_truncate() will be called on it even if it is not a regular file.
Fix this by checking the file type in this case too.

Signed-off-by: Miklos Szeredi 
Signed-off-by: Al Viro

get rid of ->mnt_longterm

2012-07-14T12:32:47+00:00

it's enough to set ->mnt_ns of internal vfsmounts to something
distinct from all struct mnt_namespace out there; then we can
just use the check for ->mnt_ns != NULL in the fast path of
mntput_no_expire()

Signed-off-by: Al Viro

vfs: split __dentry_open()

2012-06-01T16:12:00+00:00

Split __dentry_open() into two functions:

  do_dentry_open() - does most of the actual work, doesn't put file on failure
  open_check_o_direct() - after a successful open, checks direct_IO method

This will allow i_op->atomic_open to do just the file initialization and leave
the direct_IO checking to the VFS.

Signed-off-by: Miklos Szeredi 
Signed-off-by: Al Viro

brlocks/lglocks: turn into functions

2012-05-30T03:28:41+00:00

lglocks and brlocks are currently generated with some complicated macros
in lglock.h.  But there's no reason to not just use common utility
functions and put all the data into a common data structure.

Since there are at least two users it makes sense to share this code in a
library.  This is also easier maintainable than a macro forest.

This will also make it later possible to dynamically allocate lglocks and
also use them in modules (this would both still need some additional, but
now straightforward, code)

[akpm@linux-foundation.org: checkpatch fixes]
Signed-off-by: Andi Kleen 
Cc: Al Viro 
Cc: Rusty Russell 
Signed-off-by: Andrew Morton 
Signed-off-by: Rusty Russell 
Signed-off-by: Al Viro