From owner-freebsd-stable@FreeBSD.ORG Sat Mar 11 02:03:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBC0116AC81 for ; Sat, 11 Mar 2006 02:02:56 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D05A4AE62 for ; Fri, 10 Mar 2006 22:04:54 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 17FBE1A3C2C; Fri, 10 Mar 2006 14:04:54 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0848751965; Fri, 10 Mar 2006 17:04:53 -0500 (EST) Date: Fri, 10 Mar 2006 17:04:52 -0500 From: Kris Kennaway To: Miguel Lopes Santos Ramos Message-ID: <20060310220452.GA33878@xor.obsecurity.org> References: <20060309032802.GA57404@xor.obsecurity.org> <200603090353.k293rJ6j004298@compaq.anjos.strangled.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <200603090353.k293rJ6j004298@compaq.anjos.strangled.net> User-Agent: Mutt/1.4.2.1i Cc: kuriyama@imgsrc.co.jp, freebsd-stable@freebsd.org, kris@obsecurity.org Subject: Re: rpc.lockd brokenness (2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2006 02:03:02 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I did some further testing and it turns out that rpc.lockd is broken in some cases when operating over NFSv2 (this is the default for nfs root mounts). Tracing the lock traffic I see the client making a request, the server replying but the client never acting on the reply (or never receiving it), so it just retransmits every 20 seconds forever. I'm not yet sure whether this is a regression in 6.x or another case that was broken forever. Unfortunately there's currently no option to use NFSv3 for nfs root mounts to work around this (unless you're using bootp), but it should just be a trivial matter of adding "| NFSMNT_NFSV3" to the flags in nfsclient/nfs_diskless.c:nfs_setup_diskless(): nd->root_args.flags = (NFSMNT_WSIZE | NFSMNT_RSIZE | NFSMNT_RESVPORT); Kris --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEEfgEWry0BWjoQKURAvNAAKDWUNShTEipgizfjg0xK9IUwWqhbwCfV47r MORrP7OQ+DS1MDjIYC+Jz48= =lBoF -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI--