Merge branch 'vfs-scale-working' of git://git.kernel.org/pub/scm/linux/kernel/git...

* 'vfs-scale-working' of git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin:
  fs: fix do_last error case when need_reval_dot
  nfs: add missing rcu-walk check
  fs: hlist UP debug fixup
  fs: fix dropping of rcu-walk from force_reval_path
  fs: force_reval_path drop rcu-walk before d_invalidate
  fs: small rcu-walk documentation fixes

Fixed up trivial conflicts in Documentation/filesystems/porting

diff --cc Documentation/filesystems/porting
index 266d2059b9b8d29a387ce2ef057fd995057542e8,7fcac6393cd0c5d948b4bcc285011745748d03ae..dfbcd1b00b0ae3eac43f0744646f44a88f81cfcc
--- 1/Documentation/filesystems/porting
--- 2/Documentation/filesystems/porting
+++ b/Documentation/filesystems/porting
@@@ -383,14 -383,5 +383,14 @@@ Documentation/filesystems/vfs.txt for m
  
        permission and check_acl are inode permission checks that are called
  on many or all directory inodes on the way down a path walk (to check for
- exec permission). These must now be rcu-walk aware (flags & IPERM_RCU). See
- Documentation/filesystems/vfs.txt for more details.
+ exec permission). These must now be rcu-walk aware (flags & IPERM_FLAG_RCU).
+ See Documentation/filesystems/vfs.txt for more details.
 + 
 +--
 +[mandatory]
 +      In ->fallocate() you must check the mode option passed in.  If your
 +filesystem does not support hole punching (deallocating space in the middle of a
 +file) you must return -EOPNOTSUPP if FALLOC_FL_PUNCH_HOLE is set in mode.
 +Currently you can only have FALLOC_FL_PUNCH_HOLE with FALLOC_FL_KEEP_SIZE set,
 +so the i_size should not change when hole punching, even when puching the end of
 +a file off.

diff --cc fs/namei.c
Simple merge

diff --cc fs/nfs/dir.c
Simple merge