From: NeilBrown <neilb@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Use monotonic time stamps in sunrpc auth cache.
Date: Thu, 12 Aug 2010 16:55:21 +1000 [thread overview]
Message-ID: <20100812064957.3408.44224.stgit@localhost.localdomain> (raw)
A 6 month release cycles seems to be popular these days, and it is six
months since I last posted these, so I guess it is time to post them
again (yes, I've been busy and forgot all about them - but I still
think they are important).
If you set your system time backwards, nfsd can end up caching things
much longer than it should. And if you set if very far forward,
caches will get flushed too early.
So change all time keeping to use a monotonic time based on
getboottime.
A few issues were raised last time I posted these:
http://www.spinics.net/lists/linux-nfs/msg11515.html
I think they have all been addressed now.
Thanks,
NeilBrown
---
NeilBrown (2):
sunrpc: extract some common sunrpc_cache code from nfsd
sunrpc: use monotonic time in expiry cache
fs/nfs/dns_resolve.c | 6 +++---
fs/nfsd/export.c | 9 +++------
fs/nfsd/nfs4idmap.c | 2 +-
include/linux/sunrpc/cache.h | 23 ++++++++++++++++++++++-
net/sunrpc/cache.c | 37 ++++++++++++++++++++-----------------
5 files changed, 49 insertions(+), 28 deletions(-)
--
next reply other threads:[~2010-08-12 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 6:55 NeilBrown [this message]
2010-08-12 6:55 ` [PATCH 2/2] sunrpc: use monotonic time in expiry cache NeilBrown
2010-08-24 18:15 ` J. Bruce Fields
2010-08-24 23:12 ` Neil Brown
2010-08-25 16:09 ` J. Bruce Fields
2010-08-12 6:55 ` [PATCH 1/2] sunrpc: extract some common sunrpc_cache code from nfsd NeilBrown
[not found] ` <20100812065522.3408.34827.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-08-20 22:18 ` J. Bruce Fields
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=20100812064957.3408.44224.stgit@localhost.localdomain \
--to=neilb@suse.de \
--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 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).