nfsd: return errors, not NULL, from export functions
authorJ. Bruce Fields <bfields@citi.umich.edu>
Thu, 19 Jul 2007 08:49:18 +0000 (01:49 -0700)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Thu, 19 Jul 2007 17:04:52 +0000 (10:04 -0700)
commit9a25b96c1f6e1a3c85c9524f3046c7c75d8fecc7
treeaacaf5f3616f7e24a6fe66b5df136b521ccaa557
parenta280df32db291f41b3922ac218674be526af5b9b
nfsd: return errors, not NULL, from export functions

I converted the various export-returning functions to return -ENOENT instead
of NULL, but missed a few cases.

This particular case could cause actual bugs in the case of a krb5 client that
doesn't match any ip-based client and that is trying to access a filesystem
not exported to krb5 clients.

Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
Acked-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/nfsd/export.c