From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 01:43:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B61A1065670; Thu, 13 Nov 2008 01:43:38 +0000 (UTC) (envelope-from faber@zod.isi.edu) Received: from zod.isi.edu (zod.isi.edu [128.9.168.221]) by mx1.freebsd.org (Postfix) with ESMTP id 3C4E18FC17; Thu, 13 Nov 2008 01:43:38 +0000 (UTC) (envelope-from faber@zod.isi.edu) Received: from zod.isi.edu (localhost [127.0.0.1]) by zod.isi.edu (8.14.3/8.14.3) with ESMTP id mAD1K9IS017114; Wed, 12 Nov 2008 17:20:09 -0800 (PST) (envelope-from faber@zod.isi.edu) Received: (from faber@localhost) by zod.isi.edu (8.14.3/8.14.3/Submit) id mAD1K9l3017113; Wed, 12 Nov 2008 17:20:09 -0800 (PST) (envelope-from faber) Date: Wed, 12 Nov 2008 17:20:09 -0800 From: Ted Faber To: Derek Taylor , freebsd-current@freebsd.org, dfr@freebsd.org Message-ID: <20081113012009.GA2904@zod.isi.edu> References: <20081112150850.GC34909@psu.edu> <20081113001804.GA10822@insightsol.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <20081113001804.GA10822@insightsol.com> User-Agent: Mutt/1.4.2.3i X-url: http://www.isi.edu/~faber Cc: Subject: Re: problems with nfsd (due to RPCSEC_GSS changes?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 13 Nov 2008 01:43:38 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 12, 2008 at 04:18:04PM -0800, Navdeep Parhar wrote: > On Wed, Nov 12, 2008 at 10:08:50AM -0500, Derek Taylor wrote: > > On Tue, 11 Nov 2008, Navdeep Parhar wrote: > > >Ultimately, I had to add NFS_LEGACYRPC in order to get a working nfsd. > > >Looks like there may be a problem with the new code that was added as > > >part of RPCSEC_GSS support. Note that I did not enable KGSSAPI in my > > >kernel as I have no need for it. > >=20 > > It sounds like you were bitten by the behavior documented in paragraph > > two of the commit log: > > The NFS code currently contains support for both the new RPC > > implementation and the older legacy implementation inherited > > from the original NFS codebase. The default is to use the new > > implementation - add the NFS_LEGACYRPC option to fall back to > > the old code. When I merge this support back to RELENG_7, I > > will probably change this so that users have to 'opt in' to > > get the new code. >=20 > My reading of the commit log was that the new code would work out of > the box, and that NFS_LEGACYRPC was for unforeseen problems (just like > the one I ran into). I expected the new RPC implementation to work > without any change to kernel conf or anything else. >=20 > I don't feel any expected brokenness was documented in that paragraph. For what it's worth, I made a similar transition and the new RPC code paniced my NFS client. At least, I believe that was the cause as the panic has been removed by reverting back to the old RPC code. I think this is probably worth a HEADS UP or an entry in UPDATING. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkbgMgACgkQaUz3f+Zf+XuYBgCgrkwLgl6jNyoJwRgBSHnZeLS2 P3MAoPowwsGOqgnn18r5q8Fz09iaKrFp =qiZT -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq--