1. 15 11月, 2012 11 次提交
  2. 13 11月, 2012 11 次提交
  3. 11 11月, 2012 2 次提交
  4. 08 11月, 2012 13 次提交
  5. 02 10月, 2012 3 次提交
    • J
      nfsd4: don't allow reclaims of expired clients · 0d22f68f
      J. Bruce Fields 提交于
      When a confirmed client expires, we normally also need to expire any
      stable storage record which would allow that client to reclaim state on
      the next boot.  We forgot to do this in some cases.  (For example, in
      destroy_clientid, and in the cases in exchange_id and create_session
      that destroy and existing confirmed client.)
      
      But in most other cases, there's really no harm to calling
      nfsd4_client_record_remove(), because it is a no-op in the case the
      client doesn't have an existing
      
      The single exception is destroying a client on shutdown, when we want to
      keep the stable storage records so we can recognize which clients will
      be allowed to reclaim when we come back up.
      Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      0d22f68f
    • J
      nfsd4: remove redundant callback probe · 6a3b1563
      J. Bruce Fields 提交于
      Both nfsd4_init_conn and alloc_init_session are probing the callback
      channel, harmless but pointless.
      
      Also, nfsd4_init_conn should probably be probing in the "unknown" case
      as well.  In fact I don't see any harm to just doing it unconditionally
      when we get a new backchannel connection.
      Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      6a3b1563
    • J
      nfsd4: expire old client earlier · 8f9d3d3b
      J. Bruce Fields 提交于
      Before we had to delay expiring a client till we'd found out whether the
      session and connection allocations would succeed.  That's no longer
      necessary.
      Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      8f9d3d3b