[PATCH 00/10] nfsd:refactor nfsd4_create_file()

nfs4_create_file() duplicates knowledge about opening a file which
exists in the VFS, mostly in lookup_open().  It does use dentry_create()
which shares some code, but there is more code that could be shared.

The nfsd code doesn't get some details quite right, particularly patch
05 shows this.

I hope to introduce a new VFS interface which encapulates more of what
nfsd needs and shares more code with lookup_open().  I particularly want
this as it will simplify some changes to locking rules that I am working
on.

This series re-arranges the nfsd code to get it ready for switching to
the new interface.  Once that interface lands we can then switch over
fairly easily.  Hopefully the series helps clarity even before that
happens.

The series is against nfsd-testing.

Thanks,
NeilBrown.


 [PATCH 01/10] nfsd: replace fh_fill_both_attrs() with
 [PATCH 02/10] nfsd: move fh_want_write() after preamble in
 [PATCH 03/10] nfsd: move more nfs-specific code into preamble of
 [PATCH 04/10] nfsd: remove subtlety from nfsd4_create_file()
 [PATCH 05/10] nfsd: in nfsd4_create_file() let VFS report if file was
 [PATCH 06/10] nfsd: nfsd4_create_file(): remove NFSD_MAY_CREATE
 [PATCH 07/10] nfsd: reduce range of directory lock in
 [PATCH 08/10] nfsd: open-code nfsd4_vfs_create() into
 [PATCH 09/10] nfsd: move some code out of the d_really_is_negative()
 [PATCH 10/10] nfsd: reduce want-write range in nfsd4_create_file(