Date: Thu, 4 Jun 2009 20:24:49 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Robert Watson <rwatson@FreeBSD.org> Cc: dfr@freebsd.org, freebsd-current@freebsd.org Subject: Re: Kernel panic when accessing ZFS-Filesystem via NFS Message-ID: <20090604201810.K12292@maildrop.int.zabbadoz.net> In-Reply-To: <alpine.BSF.2.00.0906041148140.74158@fledge.watson.org> References: <20090601182012.GA21543@darkthrone.kvedulv.de> <20090603121307.GA15659@hades.panopticon> <20090603152810.GA21014@atarininja.org> <20090603160945.GC21014@atarininja.org> <20090603184215.L12292@maildrop.int.zabbadoz.net> <942C18EE-0453-4568-B835-8379966F0B8A@rabson.org> <alpine.BSF.2.00.0906041126510.74158@fledge.watson.org> <alpine.BSF.2.00.0906041148140.74158@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Jun 2009, Robert Watson wrote: Hi, > Thinking more formally about this, I guess the question is whether or not the > NFS server should really be a "third" credential root. If so, we should I am not sure that would be a good idea or if it will actually be needed. I'd like to avoid adding more cases of this, especially outside init_main.c nfs server to my understanding is in no way special; nfs client would be as it can be used for the root fs. I wonder if the nfs server should use the credentials from the `prison' that triggered things off and that would be serving the data; that would probably also solve a few virtual network stack cases that are still left on my todo list. Unfortunately I'll still need stom time and probably a pencil to inhale the `new' way NFS works. /bz -- Bjoern A. Zeeb The greatest risk is not taking one.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090604201810.K12292>