From owner-freebsd-current@freebsd.org Fri Dec 13 10:52:30 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B30151CA22B for ; Fri, 13 Dec 2019 10:52:30 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [46.19.33.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47Z6v06hlxz3P1n for ; Fri, 13 Dec 2019 10:52:28 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 47Z6tr6Hz3z3wbk; Fri, 13 Dec 2019 11:52:20 +0100 (CET) From: Evilham To: Rick Macklem Cc: "freebsd-current@FreeBSD.org" Subject: Re: Heads up: Large patch that adds NFSv4.2 has been committed to head/current References: In-reply-to: Date: Fri, 13 Dec 2019 11:52:18 +0100 Message-ID: <520420b9-48ea-4a49-84db-5e30336ef091@yggdrasil.evilham.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 47Z6v06hlxz3P1n X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 46.19.33.155 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-6.48 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-3.68)[ip: (-9.85), ipnet: 46.19.32.0/21(-4.92), asn: 196752(-3.64), country: NL(0.02)]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:46.19.32.0/21, country:NL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2019 10:52:30 -0000 On dv., des. 13 2019, Rick Macklem wrote: > Hi, > > r355677 is a large patch that adds NFSv4.2 support to the NFS > client/server. > It has survived a "make universe" for all arches that would > build (some mips > and sparc64 failed for reasons unrelated to this patch). > However, I have not been able to do a build with a recent GCC. > If there are build problems, please let me know. > > Although there are a lot of code changes, they should not affect > the other > versions of NFS. The patch does add two new sysctls that can be > used to > limit the minor versions of NFSv4 supported by the nfsd and, as > such, NFSv4.2 > can be disabled without reverting this patch. > > It does change the internal interface between the NFS modules, > so they must > all be upgraded simultaneously. Although arguably not necessary, > I will do a > version bump for this. > > Hopefully this big patch does not cause you grief, rick Maybe for your relief: it looks like that build is working for me :-), so no unintended non-NFS consequences here. # uname -KiprsU FreeBSD 13.0-CURRENT amd64 GENERIC-NODEBUG 1300066 1300066 Hopefully I can test NFS 4.2 soon. Thank you for working on this! -- Evilham