From: "J. Bruce Fields" <bfields@redhat.com>
To: linux-nfs@vger.kernel.org
Subject: nfsd: pin clients to 4.0/4.1
Date: Mon, 1 Oct 2012 13:43:46 -0400 [thread overview]
Message-ID: <1349113428-30173-1-git-send-email-bfields@redhat.com> (raw)
The following patches should prevent clients from mixing 4.0 and 4.1
compounds, closing out another minor 4.1 todo. (Though it would
probably be a good idea to write some pynfs tests for some of these odd
cases.)
--b.
next reply other threads:[~2012-10-01 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 17:43 J. Bruce Fields [this message]
2012-10-01 17:43 ` [PATCH 1/2] nfsd4: set cl_minorversion at create time J. Bruce Fields
2012-10-01 17:43 ` [PATCH 2/2] nfsd4: enforce per-client sessions/no-sessions distinction 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=1349113428-30173-1-git-send-email-bfields@redhat.com \
--to=bfields@redhat.com \
--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).