Date: Fri, 10 Mar 2006 17:04:52 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Miguel Lopes Santos Ramos <miguel@anjos.strangled.net> Cc: kuriyama@imgsrc.co.jp, freebsd-stable@freebsd.org, kris@obsecurity.org Subject: Re: rpc.lockd brokenness (2) Message-ID: <20060310220452.GA33878@xor.obsecurity.org> In-Reply-To: <200603090353.k293rJ6j004298@compaq.anjos.strangled.net> References: <20060309032802.GA57404@xor.obsecurity.org> <200603090353.k293rJ6j004298@compaq.anjos.strangled.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060310220452.GA33878>