1. 16 12月, 2009 1 次提交
  2. 15 12月, 2009 1 次提交
  3. 24 9月, 2009 1 次提交
  4. 10 8月, 2009 2 次提交
  5. 24 4月, 2008 1 次提交
    • 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
  6. 02 2月, 2008 3 次提交
  7. 10 10月, 2007 1 次提交
  8. 01 8月, 2007 1 次提交
  9. 18 7月, 2007 1 次提交
    • J
      knfsd: nfsd: set rq_client to ip-address-determined-domain · 3ab4d8b1
      J. Bruce Fields 提交于
      We want it to be possible for users to restrict exports both by IP address and
      by pseudoflavor.  The pseudoflavor information has previously been passed
      using special auth_domains stored in the rq_client field.  After the preceding
      patch that stored the pseudoflavor in rq_pflavor, that's now superfluous; so
      now we use rq_client for the ip information, as auth_null and auth_unix do.
      
      However, we keep around the special auth_domain in the rq_gssclient field for
      backwards compatibility purposes, so we can still do upcalls using the old
      "gss/pseudoflavor" auth_domain if upcalls using the unix domain to give us an
      appropriate export.  This allows us to continue supporting old mountd.
      
      In fact, for this first patch, we always use the "gss/pseudoflavor"
      auth_domain (and only it) if it is available; thus rq_client is ignored in the
      auth_gss case, and this patch on its own makes no change in behavior; that
      will be left to later patches.
      
      Note on idmap: I'm almost tempted to just replace the auth_domain in the idmap
      upcall by a dummy value--no version of idmapd has ever used it, and it's
      unlikely anyone really wants to perform idmapping differently depending on the
      where the client is (they may want to perform *credential* mapping
      differently, but that's a different matter--the idmapper just handles id's
      used in getattr and setattr).  But I'm updating the idmapd code anyway, just
      out of general backwards-compatibility paranoia.
      Signed-off-by: N"J. Bruce Fields" <bfields@citi.umich.edu>
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      3ab4d8b1
  10. 09 5月, 2007 1 次提交
  11. 15 2月, 2007 1 次提交
    • T
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau 提交于
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: NTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  12. 27 9月, 2006 1 次提交
  13. 01 7月, 2006 1 次提交
  14. 28 3月, 2006 3 次提交
  15. 08 9月, 2005 1 次提交
    • B
      [PATCH] sunrpc: cache_register can use wrong module reference · f35279d3
      Bruce Allan 提交于
      When registering an RPC cache, cache_register() always sets the owner as the
      sunrpc module.  However, there are RPC caches owned by other modules.  With
      the incorrect owner setting, the real owning module can be removed potentially
      with an open reference to the cache from userspace.
      
      For example, if one were to stop the nfs server and unmount the nfsd
      filesystem, the nfsd module could be removed eventhough rpc.idmapd had
      references to the idtoname and nametoid caches (i.e.
      /proc/net/rpc/nfs4.<cachename>/channel is still open).  This resulted in a
      system panic on one of our machines when attempting to restart the nfs
      services after reloading the nfsd module.
      
      The following patch adds a 'struct module *owner' field in struct
      cache_detail.  The owner is further assigned to the struct proc_dir_entry
      in cache_register() so that the module cannot be unloaded while user-space
      daemons have an open reference on the associated file under /proc.
      Signed-off-by: NBruce Allan <bwa@us.ibm.com>
      Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
      Cc: Neil Brown <neilb@cse.unsw.edu.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      f35279d3
  16. 24 6月, 2005 1 次提交
  17. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4