1. 04 4月, 2009 9 次提交
  2. 30 3月, 2009 1 次提交
  3. 28 3月, 2009 1 次提交
  4. 19 3月, 2009 7 次提交
  5. 31 1月, 2009 1 次提交
  6. 30 1月, 2009 2 次提交
  7. 08 1月, 2009 1 次提交
  8. 07 1月, 2009 1 次提交
  9. 24 12月, 2008 2 次提交
  10. 30 9月, 2008 1 次提交
    • J
      nfsd: permit unauthenticated stat of export root · 04716e66
      J. Bruce Fields 提交于
      RFC 2623 section 2.3.2 permits the server to bypass gss authentication
      checks for certain operations that a client may perform when mounting.
      In the case of a client that doesn't have some form of credentials
      available to it on boot, this allows it to perform the mount unattended.
      (Presumably real file access won't be needed until a user with
      credentials logs in.)
      
      Being slightly more lenient allows lots of old clients to access
      krb5-only exports, with the only loss being a small amount of
      information leaked about the root directory of the export.
      
      This affects only v2 and v3; v4 still requires authentication for all
      access.
      
      Thanks to Peter Staubach testing against a Solaris client, which
      suggesting addition of v3 getattr, to the list, and to Trond for noting
      that doing so exposes no additional information.
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      Cc: Peter Staubach <staubach@redhat.com>
      Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
      04716e66
  11. 26 7月, 2008 1 次提交
  12. 24 6月, 2008 4 次提交
  13. 26 4月, 2008 1 次提交
  14. 24 4月, 2008 2 次提交
    • R
      NFSD: Strip __KERNEL__ testing from unexported header files. · a5ae0398
      Robert P. J. Day 提交于
      Also, sort the Kbuild file.
      Signed-off-by: NRobert P. J. Day <rpjday@crashcourse.ca>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      a5ae0398
    • H
      nfsd: fix sparse warnings · a254b246
      Harvey Harrison 提交于
      Add extern to nfsd/nfsd.h
      fs/nfsd/nfssvc.c:146:5: warning: symbol 'nfsd_nrthreads' was not declared. Should it be static?
      fs/nfsd/nfssvc.c:261:5: warning: symbol 'nfsd_nrpools' was not declared. Should it be static?
      fs/nfsd/nfssvc.c:269:5: warning: symbol 'nfsd_get_nrthreads' was not declared. Should it be static?
      fs/nfsd/nfssvc.c:281:5: warning: symbol 'nfsd_set_nrthreads' was not declared. Should it be static?
      fs/nfsd/export.c:1534:23: warning: symbol 'nfs_exports_op' was not declared. Should it be static?
      
      Add include of auth.h
      fs/nfsd/auth.c:27:5: warning: symbol 'nfsd_setuser' was not declared. Should it be static?
      
      Make static, move forward declaration closer to where it's needed.
      fs/nfsd/nfs4state.c:1877:1: warning: symbol 'laundromat_main' was not declared. Should it be static?
      
      Make static, forward declaration was already marked static.
      fs/nfsd/nfs4idmap.c:206:1: warning: symbol 'idtoname_parse' was not declared. Should it be static?
      fs/nfsd/vfs.c:1156:1: warning: symbol 'nfsd_create_setattr' was not declared. Should it be static?
      Signed-off-by: NHarvey Harrison <harvey.harrison@gmail.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      a254b246
  15. 15 2月, 2008 2 次提交
  16. 02 2月, 2008 4 次提交
    • F
      nfsd: Allow AIX client to read dir containing mountpoints · 406a7ea9
      Frank Filz 提交于
      This patch addresses a compatibility issue with a Linux NFS server and
      AIX NFS client.
      
      I have exported /export as fsid=0 with sec=krb5:krb5i
      I have mount --bind /home onto /export/home
      I have exported /export/home with sec=krb5i
      
      The AIX client mounts / -o sec=krb5:krb5i onto /mnt
      
      If I do an ls /mnt, the AIX client gets a permission error. Looking at
      the network traceIwe see a READDIR looking for attributes
      FATTR4_RDATTR_ERROR and FATTR4_MOUNTED_ON_FILEID. The response gives a
      NFS4ERR_WRONGSEC which the AIX client is not expecting.
      
      Since the AIX client is only asking for an attribute that is an
      attribute of the parent file system (pseudo root in my example), it
      seems reasonable that there should not be an error.
      
      In discussing this issue with Bruce Fields, I initially proposed
      ignoring the error in nfsd4_encode_dirent_fattr() if all that was being
      asked for was FATTR4_RDATTR_ERROR and FATTR4_MOUNTED_ON_FILEID, however,
      Bruce suggested that we avoid calling cross_mnt() if only these
      attributes are requested.
      
      The following patch implements bypassing cross_mnt() if only
      FATTR4_RDATTR_ERROR and FATTR4_MOUNTED_ON_FILEID are called. Since there
      is some complexity in the code in nfsd4_encode_fattr(), I didn't want to
      duplicate code (and introduce a maintenance nightmare), so I added a
      parameter to nfsd4_encode_fattr() that indicates whether it should
      ignore cross mounts and simply fill in the attribute using the passed in
      dentry as opposed to it's parent.
      Signed-off-by: NFrank Filz <ffilzlnx@us.ibm.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      406a7ea9
    • J
      nfsd: move nfsd/auth.h into fs/nfsd · 2e8138a2
      J. Bruce Fields 提交于
      This header is used only in a few places in fs/nfsd, so there seems to
      be little point to having it in include/.  (Thanks to Robert Day for
      pointing this out.)
      
      Cc: Robert P. J. Day <rpjday@crashcourse.ca>
      Acked-by: NNeilBrown <neilb@suse.de>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      2e8138a2
    • J
      knfsd: allow cache_register to return error on failure · dbf847ec
      J. Bruce Fields 提交于
      Newer server features such as nfsv4 and gss depend on proc to work, so a
      failure to initialize the proc files they need should be treated as
      fatal.
      
      Thanks to Andrew Morton for style fix and compile fix in case where
      CONFIG_NFSD_V4 is undefined.
      
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Acked-by: NNeilBrown <neilb@suse.de>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      dbf847ec
    • J
      nfsd: fail module init on reply cache init failure · d5c3428b
      J. Bruce Fields 提交于
      If the reply cache initialization fails due to a kmalloc failure,
      currently we try to soldier on with a reduced (or nonexistant) reply
      cache.
      
      Better to just fail immediately: the failure is then much easier to
      understand and debug, and it could save us complexity in some later
      code.  (But actually, it doesn't help currently because the cache is
      also turned off in some odd failure cases; we should probably find a
      better way to handle those failure cases some day.)
      
      Fix some minor style problems while we're at it, and rename
      nfsd_cache_init() to remove the need for a comment describing it.
      Acked-by: NNeilBrown <neilb@suse.de>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      d5c3428b