1. 30 4月, 2011 1 次提交
    • J
      nfsd4: fix wrongsec handling for PUTFH + op cases · 68d93184
      J. Bruce Fields 提交于
      When PUTFH is followed by an operation that uses the filehandle, and
      when the current client is using a security flavor that is inconsistent
      with the given filehandle, we have a choice: we can return WRONGSEC
      either when the current filehandle is set using the PUTFH, or when the
      filehandle is first used by the following operation.
      
      Follow the recommendations of RFC 5661 in making this choice.
      
      (Our current behavior prevented the client from doing security
      negotiation by returning WRONGSEC on PUTFH+SECINFO_NO_NAME.)
      Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      68d93184
  2. 11 4月, 2011 4 次提交
  3. 10 4月, 2011 1 次提交
    • J
      svcrpc: complete svsk processing on cb receive failure · 8985ef0b
      J. Bruce Fields 提交于
      Currently when there's some failure to receive a callback (because we
      couldn't find a matching xid, for example), we exit svc_recv with
      sk_tcplen still set but without any pages saved with the socket.  This
      will cause a crash later in svc_tcp_restore_pages.
      
      Instead, make sure we reset that tcp information whether the callback
      received failed or succeeded.
      Signed-off-by: NJ. Bruce Fields <bfields@redhat.com>
      8985ef0b
  4. 08 4月, 2011 8 次提交
  5. 06 4月, 2011 20 次提交
  6. 05 4月, 2011 6 次提交