diff options
| author | Stanislav Kinsbursky <skinsbursky@parallels.com> | 2010-12-08 12:40:13 +0300 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-12-21 11:51:25 -0500 |
| commit | aa69947399a119d7f1b35bbcd62c849839b35449 (patch) | |
| tree | adc7362f5e8240c1c0086af0b912d3013cef10c9 /net/sunrpc | |
| parent | 611c96c8f728c4bcdbadaa2387942d3c0641cadf (diff) | |
| download | blackbird-op-linux-aa69947399a119d7f1b35bbcd62c849839b35449.tar.gz blackbird-op-linux-aa69947399a119d7f1b35bbcd62c849839b35449.zip | |
NFS: suppressing showing of default mount port value in /proc fixed
Update: added check for zero value as it was before (note: can't simply check
mountd_port for positive value because it's typeof unsigned short)
Default value for mount server port is set to NFS_UNSPEC_PORT (-1) and will not
be changed during parsing mount options for mound data version 6. This default
value will be showed for mountport in /proc/mounts always since current default
check is for zero value. This small mistake leads to big problem, because
during umount.nfs execution from old user-space utils (at least nfs-utils
1.0.9) this value will be used as the server port to connect to. This request
will be rejected (since port is 65535) and thus nfs mount point can't be
unmounted.
Note from Chuck Lever (chuck.lever@oracle.com): this is only possible if
/etc/mtab is a link to /proc/mounts. Not all systems have this configuration.
Signed-off-by: Stanislav Kinsbursky <skinsbursky@parallels.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'net/sunrpc')
0 files changed, 0 insertions, 0 deletions
