From: Harshula <harshula@redhat.com>
To: andros@netapp.com, "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: RPC_CRED_KEY_EXPIRE_SOON and RPC_CRED_NO_CRKEY_TIMEOUT
Date: Wed, 02 Mar 2016 00:17:14 +1100 [thread overview]
Message-ID: <1456838234.2814.89.camel@redhat.com> (raw)
Hi Andy & Bruce,
re: Commit dc24826bfca8d788d05f625208f06d90be5560b3 (NFS avoid expired
credential keys for buffered writes)
Is it a valid state for ac_flags to have RPC_CRED_KEY_EXPIRE_SOON and
RPC_CRED_NO_CRKEY_TIMEOUT set at the same time?
reply other threads:[~2016-03-01 13:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1456838234.2814.89.camel@redhat.com \
--to=harshula@redhat.com \
--cc=andros@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.