Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1212770

Bug#711021: mount.nfs timeout for GETPORT is much too short

From Salvatore Bonaccorso <carnil@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#711021: mount.nfs timeout for GETPORT is much too short
Date 2024-09-13 23:10 +0200
Message-ID <JmlId-c3Uz-5@gated-at.bofh.it> (permalink)
References <lgPDA-1IM-5@gated-at.bofh.it> <lgPDA-1IM-5@gated-at.bofh.it> <E2NyF-2QPR-1@gated-at.bofh.it> <lgPDA-1IM-5@gated-at.bofh.it> <E2NyF-2QPR-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Hi Ben,

On Sat, Mar 19, 2022 at 08:58:46PM +0100, Ben Hutchings wrote:
> 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!

Is this still something we need to report upstream? (And if so, could
you do it?).

Regards,
Salvatore

Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread


Thread

Bug#711021: mount.nfs timeout for GETPORT is much too short Salvatore Bonaccorso <carnil@debian.org> - 2024-09-13 23:10 +0200

csiph-web