Fwd: [PATCH v1 0/2] Improve construction of non-UCS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Trond-

> Begin forwarded message:
> 
> From: Chuck Lever <chuck.lever@xxxxxxxxxx>
> Subject: [PATCH v1 0/2] Improve construction of non-UCS
> Date: June 4, 2018 at 10:53:23 AM EDT
> To: linux-nfs@xxxxxxxxxxxxxxx
> 
> 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(-)

Are you building the official NFS client PR for this merge window?
Would you consider taking this series?


--
Chuck Lever



--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux