1. 07 2月, 2008 27 次提交
  2. 04 2月, 2008 5 次提交
  3. 03 2月, 2008 4 次提交
  4. 02 2月, 2008 4 次提交
    • J
      NLM: tear down RPC clients in nlm_shutdown_hosts · d801b861
      Jeff Layton 提交于
      It's possible for a RPC to outlive the lockd daemon that created it, so
      we need to make sure that all RPC's are killed when lockd is coming
      down. When nlm_shutdown_hosts is called, kill off all RPC tasks
      associated with the host. Since we need to wait until they have all gone
      away, we might as well just shut down the RPC client altogether.
      Signed-off-by: NJeff Layton <jlayton@redhat.com>
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      d801b861
    • J
      nfsd: more careful input validation in nfsctl write methods · 87d26ea7
      J. Bruce Fields 提交于
      Neil Brown points out that we're checking buf[size-1] in a couple places
      without first checking whether size is zero.
      
      Actually, given the implementation of simple_transaction_get(), buf[-1]
      is zero, so in both of these cases the subsequent check of the value of
      buf[size-1] will catch this case.
      
      But it seems fragile to depend on that, so add explicit checks for this
      case.
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      Acked-by: NNeilBrown <neilb@suse.de>
      87d26ea7
    • J
      lockd: minor log message fix · 50431d94
      J. Bruce Fields 提交于
      Wendy Cheng noticed that function name doesn't agree here.
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      Cc: Wendy Cheng <wcheng@redhat.com>
      50431d94
    • J
      knfsd: don't bother mapping putrootfh enoent to eperm · f7b8066f
      J. Bruce Fields 提交于
      Neither EPERM and ENOENT map to valid errors for PUTROOTFH according to
      rfc 3530, and, if anything, ENOENT is likely to be slightly more
      informative; so don't bother mapping ENOENT to EPERM.  (Probably this
      was originally done because one likely cause was that there is an fsid=0
      export but that it isn't permitted to this particular client.  Now that
      we allow WRONGSEC returns, this is somewhat less likely.)
      
      In the long term we should work to make this situation less likely,
      perhaps by turning off nfsv4 service entirely in the absence of the
      pseudofs root, or constructing a pseudofilesystem root ourselves in the
      kernel as necessary.
      
      Thanks to Benny Halevy <bhalevy@panasas.com> for pointing out this
      problem.
      Signed-off-by: NJ. Bruce Fields <bfields@citi.umich.edu>
      Cc: Benny Halevy <bhalevy@panasas.com>
      f7b8066f