summaryrefslogtreecommitdiffstats
path: root/fs/jffs2
diff options
context:
space:
mode:
authorTrond Myklebust <trond.myklebust@primarydata.com>2015-01-03 15:35:27 -0500
committerTrond Myklebust <trond.myklebust@primarydata.com>2015-01-05 19:40:53 -0800
commit55b9df93ddd684cbc4c2dee9b8a99f6e48348212 (patch)
tree23d80bb002807d513aa8d44d068cd7ec6f124123 /fs/jffs2
parentceb3a16c070c403f5f9ca46b46cf2bb79ea11750 (diff)
downloadlinux-55b9df93ddd684cbc4c2dee9b8a99f6e48348212.tar.gz
linux-55b9df93ddd684cbc4c2dee9b8a99f6e48348212.tar.bz2
linux-55b9df93ddd684cbc4c2dee9b8a99f6e48348212.zip
NFSv4/v4.1: Verify the client owner id during trunking detection
While we normally expect the NFSv4 client to always send the same client owner to all servers, there are a couple of situations where that is not the case: 1) In NFSv4.0, switching between use of '-omigration' and not will cause the kernel to switch between using the non-uniform and uniform client strings. 2) In NFSv4.1, or NFSv4.0 when using uniform client strings, if the uniquifier string is suddenly changed. This patch will catch those situations by checking the client owner id in the trunking detection code, and will do the right thing if it notices that the strings differ. Cc: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/jffs2')
0 files changed, 0 insertions, 0 deletions