linux.git/Documentation/filesystems/porting, branch v3.12

fs: remove vfs_follow_link

2013-09-10T21:06:45+00:00

For a long time no filesystem has been using vfs_follow_link, and as seen
by recent filesystem submissions any new use is accidental as well.

Remove vfs_follow_link, document the replacement in
Documentation/filesystems/porting and also rename __vfs_follow_link
to match its only caller better.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

[readdir] ->readdir() is gone

2013-06-29T08:57:04+00:00

everything's converted to ->iterate()

Signed-off-by: Al Viro

[readdir] introduce iterate_dir() and dir_context

2013-06-29T08:46:46+00:00

iterate_dir(): new helper, replacing vfs_readdir().

struct dir_context: contains the readdir callback (and will get more stuff
in it), embedded into whatever data that callback wants to deal with;
eventually, we'll be passing it to ->readdir() replacement instead of
(data,filldir) pair.

Signed-off-by: Al Viro

vfs: kill FS_REVAL_DOT by adding a d_weak_revalidate dentry op

2013-02-26T07:46:09+00:00

The following set of operations on a NFS client and server will cause

    server# mkdir a
    client# cd a
    server# mv a a.bak
    client# sleep 30  # (or whatever the dir attrcache timeout is)
    client# stat .
    stat: cannot stat `.': Stale NFS file handle

Obviously, we should not be getting an ESTALE error back there since the
inode still exists on the server. The problem is that the lookup code
will call d_revalidate on the dentry that "." refers to, because NFS has
FS_REVAL_DOT set.

nfs_lookup_revalidate will see that the parent directory has changed and
will try to reverify the dentry by redoing a LOOKUP. That of course
fails, so the lookup code returns ESTALE.

The problem here is that d_revalidate is really a bad fit for this case.
What we really want to know at this point is whether the inode is still
good or not, but we don't really care what name it goes by or whether
the dcache is still valid.

Add a new d_op->d_weak_revalidate operation and have complete_walk call
that instead of d_revalidate. The intent there is to allow for a
"weaker" d_revalidate that just checks to see whether the inode is still
good. This is also gives us an opportunity to kill off the FS_REVAL_DOT
special casing.

[AV: changed method name, added note in porting, fixed confusion re
having it possibly called from RCU mode (it won't be)]

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

documentation: drop vmtruncate

2012-12-20T23:47:08+00:00

Removed vmtruncate

Signed-off-by: Marco Stornelli 
Signed-off-by: Al Viro

Documentation: get rid of write_super

2012-08-03T21:25:20+00:00

The '->write_super' superblock method is gone, and this patch removes all the
references to 'write_super' from various pieces of the kernel documentation.

Cc: Randy Dunlap 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: Al Viro

don't pass nameidata to ->create()

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

boolean "does it have to be exclusive?" flag is passed instead;
Local filesystem should just ignore it - the object is guaranteed
not to be there yet.

Signed-off-by: Al Viro

stop passing nameidata to ->lookup()

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

Just the flags; only NFS cares even about that, but there are
legitimate uses for such argument.  And getting rid of that
completely would require splitting ->lookup() into a couple
of methods (at least), so let's leave that alone for now...

Signed-off-by: Al Viro

stop passing nameidata * to ->d_revalidate()

2012-07-14T12:34:14+00:00

Just the lookup flags.  Die, bastard, die...

Signed-off-by: Al Viro

vfs: update documentation on ->i_dentry handling

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

we used to need to clean it in RCU callback freeing an inode;
in 3.2 that requirement went away.  Unfortunately, it hadn't
been reflected in Documentation/filesystems/porting.

Signed-off-by: Al Viro