From nobody Tue Jan 4 02:00:12 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EF9D5191C382 for ; Tue, 4 Jan 2022 02:00:14 +0000 (UTC) (envelope-from gjb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JSbRL6RZcz57M9; Tue, 4 Jan 2022 02:00:14 +0000 (UTC) (envelope-from gjb@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1641261614; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8EUCc+i6SmuOqN4LyExhtybnbWcMKHhH69nrLnOCbZ0=; b=jh4+Q1Tf0pr/VDyi9sKy0I6vvGJIVIY40eUzstPitbrFRVjIM/I+UZwqvbDR39BlH5CkRs WN4wYGqStRY3z6jQJW+ISLXDvT8g8vjtoMkKyJSPxoesWAMO9v9IAYl3kfjDWjgO9V6c3n ldKTIU6EirwYC+66kRfASaq7QZg7mXqM53+DRBQ66N1Fg2aJvyXOpLwCRxWH9+F/8dIhSw Q2T7ZoIuwptdpPt1Azgm2DThZuq/7+xkx31EQgKFUx7XWn4JhR2Pq0HhcxwVT+r9DQI6Ba ojpN9x0Iiw7wnKcYb+ZUrfQvZMtznx3Ca4xzeebTsuYgQfCZapaJr2G6w3pmvQ== Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 5BAF3179B4; Tue, 4 Jan 2022 02:00:14 +0000 (UTC) (envelope-from gjb@freebsd.org) Date: Tue, 4 Jan 2022 02:00:12 +0000 From: Glen Barber To: Colin Percival Cc: d@delphij.net, freebsd-current , rmacklem@freebsd.org, "re@FreeBSD.org Engineering Team" Subject: Re: [RFC] Making mount_nfs to attempt NFSv4 before NFSv3 and NFSv2? Message-ID: <20220104020012.GP14836@FreeBSD.org> References: <0100017e22709d93-0c9ce998-0308-47fc-b4f0-aa4c00d795ea-000000@email.amazonses.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oNLI4EWr1RPQuPCf" Content-Disposition: inline In-Reply-To: <0100017e22709d93-0c9ce998-0308-47fc-b4f0-aa4c00d795ea-000000@email.amazonses.com> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1641261614; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8EUCc+i6SmuOqN4LyExhtybnbWcMKHhH69nrLnOCbZ0=; b=a/B5fYiWu7wllhOTouHE6XFclamskTmpMPtAPhmuLfLRpNdhGySresWrfGAbBeO9Lqbx3r R51hU3TgieQkK+8lc77uerhTqBohL4PMGSGyFJs0FbfuPoKPhAZvNdtYmRWBfOp318kRdR nbjvERUPpQ8dnfWqfMVLaGGrOs8az3WAYkYS7sN77zMor5bnfXet8ZxEiUTCHKaTVyQRvP CdrdQqi48ajT52NOyJ3SoklyWBBNp0jYzivtEi1ZKv0Ti74obo9A430u2v8NodDkr9lNlw Jh3Bz4v/MKzP7CL8X6xGxK+AcSdiX2lwp1kaQxWAu7aDomLdtYmY77AgIQk4Fg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1641261614; a=rsa-sha256; cv=none; b=JHaOcjZ0q9awmQCugRrwlYgSXH1wYY0wnI2EWYhwSmIZ0/wrLMMt719JZlO0hHjTkdDLWD +yTQQ6M5Bx6nA/vQ507UIkJVfY9C1McN/gRC7jz3036rdUXLOOJblMFnqTFs39woNh3Icg 7kSXtuAsYpnoqMrV5uRfYDvZSeLWR0AHfCFqF7GVSHXkH+38CQP7StujZUmNyio5ceaCRS 3zrEkKWw4raTCi6Q3DG9PGPq1eC6dSgbcydOptC84e3jlKS/6u7HjouEISXVZ2M6bRv4fJ EQTyvg69UFVVRNtJ82jzww4VRJR8HIW4u7VoyT9Gs3Lbafv/PvLQGot3tf0g0g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --oNLI4EWr1RPQuPCf Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 04, 2022 at 12:15:12AM +0000, Colin Percival wrote: > On 1/3/22 10:51, Xin Li wrote: > > [...] > > So I think it makes sense to teach mount_nfs to attempt NFSv4, then > > NFSv3 and NFSv2.=A0 However, this might be a POLA violation and we would > > like to know if there is any objections. >=20 > This seems like a sensible change of defaults to make in 14-CURRENT; plea= se > add an entry to RELNOTES so that users will be alerted to the change. >=20 > I don't think this should be MFCed. >=20 I am torn on the topic, and would like to hear feedback from others that use NFS (I personally do not, so this change does not affect me). I will agree with whatever is the outcome of the majority. Glen --oNLI4EWr1RPQuPCf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmHTqiwACgkQAxRYpUeP 4pMxeA/+Pk8c6vYA26fcT/6jR7G4Q+hNtZzrMEl4uvBxdh0VWiZmlezKqzsq0BbN PROHNEQRhu3H/eN1T0+VKEEpDAwGhh/TZdbXtxwqRIV9ddwEet06rAB+r4PAexYe JyYSV6fr4sVF/ZZ1fJfGaJFNXocveEcuzX4HLkxjCHwqddkKmsP7V4RwlFjRBKR1 e796YwXtLb6GQwMRTa2pZEagF3Asfg2pwdJWPzYqGtG02/a5ulQlQyQz/BpAQaD5 elzWDqyidheOIeYJcA5NdY0cKNC9kfSIg8iOXkgU1SHLJTuIQKz8Twnf5kc2Mbiz EzsFar8BKibb9pzt9jV3Kc7RmBuHrQ1vmyNcDC+qGCBI5WvqeF/oSRGrHQXdtJJU BBVNU489xeuKdOOSeqiBVxbZF+DFFp3qYo8EEHBtczP3Fz6tbbFC1LckNvB7PQwq nYp+oLhHUlh/4yeQ2OaBCrelJwQQJo6eEzlrhPvCdGNj+xaXMZpHyGxbKht3zLdh zVJRAc8xpBLHjmASzjGl8zuB+qaIC9758zo0YMg0CbQ+p9FhwWuzgCGCk+pLzfVx ysqyMXwA6HvYnuva+u1fFeaH14VsQwNiodwqNIiRmFzXZmn6i1KO/3m2JtkrNv++ fWHGhs4FYYXhH0rb1lp5PSHBfArBLn2aJ24LNRfRIpjsRi04zug= =qC+X -----END PGP SIGNATURE----- --oNLI4EWr1RPQuPCf--