From: Jim Rees <rees@umich.edu>
To: andros@netapp.com
Cc: trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] RFC Avoid expired credential keys for buffered writes
Date: Thu, 6 Sep 2012 21:36:15 -0400 [thread overview]
Message-ID: <20120907013615.GA20444@umich.edu> (raw)
In-Reply-To: <1346961251-2554-1-git-send-email-andros@netapp.com>
andros@netapp.com wrote:
From: Andy Adamson <andros@netapp.com>
This patch set is a Request for Comments: I think it does a fair job of
handling the issue - but it is complicated, and other brains might find a
better way to get the job done.
I really like it. What we're doing now is nuts. It even (mostly) solves
the old afs problem of write succeeding then having the close fail.
next prev parent reply other threads:[~2012-09-07 1:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 19:54 [PATCH 0/4] RFC Avoid expired credential keys for buffered writes andros
2012-09-06 19:54 ` [PATCH 1/4] SUNRPC handle EKEYEXPIRED in call_refreshresult andros
2012-09-06 19:54 ` [PATCH 2/4] SUNRPC set gss gc_expiry to full lifetime andros
2012-09-06 19:54 ` [PATCH 3/4] SUNRPC new rpc_credops to test credential expiry andros
2012-09-06 19:54 ` [PATCH 4/4] NFS avoid expired credential keys for buffered writes andros
2012-09-07 1:36 ` Jim Rees [this message]
2012-09-10 18:57 ` [PATCH 0/4] RFC Avoid " Jeff Layton
2012-09-10 19:52 ` Adamson, Andy
2012-09-10 20:08 ` Jeff Layton
2012-09-12 15:13 ` Adamson, Andy
2012-09-12 15:21 ` Myklebust, Trond
2012-09-12 16:14 ` Adamson, Andy
2012-09-13 17:57 ` J. Bruce Fields
2012-09-13 18:09 ` Myklebust, Trond
2012-09-13 18:21 ` J. Bruce Fields
2012-09-13 18:12 ` Adamson, Andy
2012-09-10 20:12 ` Myklebust, Trond
2012-09-10 19:56 ` Jim Rees
2012-09-10 20:14 ` Myklebust, Trond
2012-09-10 21:03 ` Adamson, Andy
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=20120907013615.GA20444@umich.edu \
--to=rees@umich.edu \
--cc=andros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).