Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1097427
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#711021: mount.nfs timeout for GETPORT is much too short |
| Date | 2022-03-19 21:10 +0100 |
| Message-ID | <E2NyF-2QPR-1@gated-at.bofh.it> (permalink) |
| References | <lgPDA-1IM-5@gated-at.bofh.it> <lgPDA-1IM-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
I'm not sure that this bug was ever fixed.
nfs-utils actually uses nfs_getport() to get the port. That passes a
timeout of {-1, 0} to libtirpc, which is invalid and should result in
using the rpcbind client's default timeout.
The TCP client interface is implemented in src/clnt_vc.c. It has a
default timeout (ct_wait field) that can be set with CLNT_CONTROL(...,
CLSET_TIMEOUT, ...), but nfs-utils doesn't seem to do that. So it
seems like there is a default timeout of 0!
Ben.
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread
Bug#711021: mount.nfs timeout for GETPORT is much too short Ben Hutchings <ben@decadent.org.uk> - 2022-03-19 21:10 +0100
csiph-web