Subject: [PATCH v1 0/2] Improve construction of non-UCS
From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Date: Mon, 04 Jun 2018 10:53:23 -0400
Message-ID: <20180604144154.11877.19298.stgit@manet.1015granger.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Sender: linux-nfs-owner@vger.kernel.org

The following series proposes improvements to the default NFSv4.0
client ID strings. The purpose is to decrease the chance that two
distinct clients will choose the same string, and to make the same
client connecting via different transports choose the same string.

The use of the nodename comes from the NFSv4.1 (uniform) client
ID string. It has some shortcomings as well, but it is better
overall than using the client's local address. The use of the
uniquifier is also copied from the uniform client ID string.

The goal is to make the default behavior better. Preventing a
malicious administrator from choosing the same nodename, uniquifier,
and/or client address on purpose is not possible.

---

Chuck Lever (2):
      NFSv4.0: Remove cl_ipaddr from non-UCS client ID
      NFSv4.0: Remove transport protocol name from non-UCS client ID


 fs/nfs/nfs4proc.c |   24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

--
Chuck Lever