1. 04 10月, 2006 2 次提交
    • O
      [PATCH] knfsd: lockd: Make nlm_host_rebooted use the nsm_handle · 5c8dd29c
      Olaf Kirch 提交于
      This patch makes the SM_NOTIFY handling understand and use the nsm_handle.
      
      To make it a bit clear what is happening:
      
          nlmclent_prepare_reclaim and nlmclnt_finish_reclaim
          get open-coded into 'reclaimer'
      
      The result is tidied up.
      
      Then some of that functionality is moved out into nlm_host_rebooted (which
      calls nlmclnt_recovery which starts a thread which runs reclaimer).
      
      Also host_rebooted now finds an nsm_handle rather than a host, then then
      iterates over all hosts and deals with each host that shares that nsm_handle.
      Signed-off-by: NOlaf Kirch <okir@suse.de>
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      5c8dd29c
    • O
      [PATCH] knfsd: lockd: introduce nsm_handle · 8dead0db
      Olaf Kirch 提交于
      This patch introduces the nsm_handle, which is shared by all nlm_host objects
      referring to the same client.
      
      With this patch applied, all nlm_hosts from the same address will share the
      same nsm_handle.  A future patch will add sharing by name.
      
      Note: this patch changes h_name so that it is no longer guaranteed to be an IP
      address of the host.  When the host represents an NFS server, h_name will be
      the name passed in the mount call.  When the host represents a client, h_name
      will be the name presented in the lock request received from the client.  A
      h_name is only used for printing informational messages, this change should
      not be significant.
      Signed-off-by: NOlaf Kirch <okir@suse.de>
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      8dead0db
  2. 02 10月, 2006 2 次提交
    • N
      [PATCH] knfsd: Correctly handle error condition from lockd_up · 4a3ae42d
      NeilBrown 提交于
      If lockd_up fails - what should we expect?  Do we have to later call
      lockd_down?
      
      Well the nfs client thinks "no", the nfs server thinks "yes".  lockd thinks
      "yes".
      
      The only answer that really makes sense is "no" !!
      
      So:
        Make lockd_up only increment  nlmsvc_users on success.
        Make nfsd handle errors from lockd_up properly.
        Make sure lockd_up(0) never fails when lockd is running
          so that the 'reclaimer' call to lockd_up doesn't need to
          be error checked.
      
      Cc: "J. Bruce Fields" <bfields@fieldses.org>
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4a3ae42d
    • N
      [PATCH] knfsd: be more selective in which sockets lockd listens on · 24e36663
      NeilBrown 提交于
      Currently lockd listens on UDP always, and TCP if CONFIG_NFSD_TCP is set.
      
      However as lockd performs services of the client as well, this is a problem.
      If CONFIG_NfSD_TCP is not set, and a tcp mount is used, the server will not be
      able to call back to lockd.
      
      So:
       - add an option to lockd_up saying which protocol is needed
       - Always open sockets for which an explicit port was given, otherwise
         only open a socket of the type required
       - Change nfsd to do one lockd_up per socket rather than one per thread.
      
      This
       - removes the dependancy on CONFIG_NFSD_TCP
       - means that lockd may open sockets other than at startup
       - means that lockd will *not* listen on UDP if the only
         mounts are TCP mount (and nfsd hasn't started).
      
      The latter is the only one that concerns me at all - I don't know if this
      might be a problem with some servers.
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      24e36663
  3. 27 9月, 2006 1 次提交
  4. 09 6月, 2006 1 次提交
  5. 21 3月, 2006 4 次提交
  6. 15 2月, 2006 1 次提交
    • T
      [PATCH] NLM: Fix the NLM_GRANTED callback checks · 5ac5f9d1
      Trond Myklebust 提交于
      If 2 threads attached to the same process are blocking on different locks on
      different files (maybe even on different servers) but have the same lock
      arguments (i.e.  same offset+length - actually quite common, since most
      processes try to lock the entire file) then the first GRANTED call that wakes
      one up will also wake the other.
      
      Currently when the NLM_GRANTED callback comes in, lockd walks the list of
      blocked locks in search of a match to the lock that the NLM server has
      granted.  Although it checks the lock pid, start and end, it fails to check
      the filehandle and the server address.
      
      By checking the filehandle and server IP address, we ensure that this only
      happens if the locks truly are referencing the same file.
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      5ac5f9d1
  7. 20 12月, 2005 1 次提交
  8. 23 6月, 2005 2 次提交
  9. 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