From: Jeff Layton <jlayton@primarydata.com>
To: steved@redhat.com
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: [PATCH v5 0/7] nfs-utils: support for lifting grace period early
Date: Fri, 19 Sep 2014 09:52:43 -0400 [thread overview]
Message-ID: <1411134770-2409-1-git-send-email-jlayton@primarydata.com> (raw)
v5:
- fix build break in middle of set
v4:
- replace "reclaim_complete" timestamp column with "has_session" boolean
- change to use NFSDCLTRACK_CLIENT_HAS_SESSION environment variable
- only set timestamp on "has_session" clients during "create" op
v3:
- account for change to NFSDCLTRACK_RECLAIM_COMPLETE env var
This is v5 of the patchset to allow the lifting of the grace period
early. The only difference from the v4 set is a fix for a build break
that was introduced in the middle of the set (mea culpa!). The end
result here should be exactly the same as in the v4 set.
At this point, Bruce has indicated that he intends to merge these patches
for v3.18, so I think this set is also ready for merge into nfs-utils.
Jeff Layton (7):
sm-notify: inform the kernel if there were no hosts to notify
nfsdcltrack: update comments in sqlite.c
nfsdcltrack: rename CLD_* constants with CLTRACK_* prefixes
nfsdcltrack: overhaul database initializtion
nfsdcltrack: update schema to v2
nfsdcltrack: grab the NFSDCLTRACK_CLIENT_HAS_SESSION env var if it's
present
nfsdcltrack: fetch NFSDCLTRACK_GRACE_START out of environment
utils/nfsdcltrack/nfsdcltrack.c | 103 ++++++++++-
utils/nfsdcltrack/sqlite.c | 388 ++++++++++++++++++++++++++++++----------
utils/nfsdcltrack/sqlite.h | 8 +-
utils/statd/sm-notify.c | 25 +++
4 files changed, 421 insertions(+), 103 deletions(-)
--
1.9.3
next reply other threads:[~2014-09-19 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 13:52 Jeff Layton [this message]
2014-09-19 13:52 ` [PATCH v5 1/7] sm-notify: inform the kernel if there were no hosts to notify Jeff Layton
2014-09-19 13:52 ` [PATCH v5 2/7] nfsdcltrack: update comments in sqlite.c Jeff Layton
2014-09-19 13:52 ` [PATCH v5 3/7] nfsdcltrack: rename CLD_* constants with CLTRACK_* prefixes Jeff Layton
2014-09-19 13:52 ` [PATCH v5 4/7] nfsdcltrack: overhaul database initializtion Jeff Layton
2014-09-19 13:52 ` [PATCH v5 5/7] nfsdcltrack: update schema to v2 Jeff Layton
2014-09-19 13:52 ` [PATCH v5 6/7] nfsdcltrack: grab the NFSDCLTRACK_CLIENT_HAS_SESSION env var if it's present Jeff Layton
2014-09-19 13:52 ` [PATCH v5 7/7] nfsdcltrack: fetch NFSDCLTRACK_GRACE_START out of environment Jeff Layton
2014-09-19 15:20 ` [PATCH v5 0/7] nfs-utils: support for lifting grace period early Steve Dickson
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=1411134770-2409-1-git-send-email-jlayton@primarydata.com \
--to=jlayton@primarydata.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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