From owner-freebsd-current@freebsd.org Sun Jun 17 14:42:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75BDA1021329 for ; Sun, 17 Jun 2018 14:42:09 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05E4C708DF for ; Sun, 17 Jun 2018 14:42:08 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w5HEg3V9060543; Sun, 17 Jun 2018 07:42:04 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w5HEg3pB060542; Sun, 17 Jun 2018 07:42:03 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806171442.w5HEg3pB060542@pdx.rh.CN85.dnsmgr.net> Subject: Re: NFSv4.1 server deficiencies fixed for ESXi client In-Reply-To: To: Rick Macklem Date: Sun, 17 Jun 2018 07:42:03 -0700 (PDT) CC: "freebsd-current@freebsd.org" , "andreas.nagy@frequentis.com" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Sun, 17 Jun 2018 14:42:09 -0000 > Hi, > > Since I posted w.r.t. issues that seem to violate the RFC, I figured I should also > post ones that identified deficiencies in the FreeBSD server. These have either > been patched in head/current or will be soon and will be MFC'd. > > - BindConnectiontoSession wasn't implemented. It is never used by the FreeBSD > client and not used during normal operation of the Linux client. > --> Now in head and will be MFC'd soon. > - OPEN_SHARE_ACCESS_WANT_NO_DELEG flag generated an error when set for > OpenDowngrade. Since OpenDowngrade never issues a delegation, no other client > sets this flag. However, since the RFC doesn't forbid it, the code in head now just > clears/ignores the flag instead of generating an error. > - ESXi client generates warnings that "2" is not a valid reason for not issuing > a delegation. Since "2" is in the list and the RFC says nothing about when each > reason is used, I don't know why it thinks it isn't valid. However, a patch that changes > the reason makes it happy and since other clients don't seem to care, this patch > will probably go in head soon. > (Until then, all it does is generate warnings.) Have you any contact with VMWare so that they might fix the issues in thier code, rather than having to put hacks in FreeBSD for these issues? Thanks, -- Rod Grimes rgrimes@freebsd.org