From owner-freebsd-current@FreeBSD.ORG  Wed Jun  3 17:40:24 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 8F8E0106566C;
	Wed,  3 Jun 2009 17:40:24 +0000 (UTC)
	(envelope-from wxs@atarininja.org)
Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158])
	by mx1.freebsd.org (Postfix) with ESMTP id 66B978FC08;
	Wed,  3 Jun 2009 17:40:24 +0000 (UTC)
	(envelope-from wxs@atarininja.org)
Received: by syn.atarininja.org (Postfix, from userid 1001)
	id BD0D85C37; Wed,  3 Jun 2009 13:40:23 -0400 (EDT)
Date: Wed, 3 Jun 2009 13:40:23 -0400
From: Wesley Shields <wxs@FreeBSD.org>
To: Dmitry Marakasov <amdmi3@amdmi3.ru>
Message-ID: <20090603174023.GA23095@atarininja.org>
References: <20090601182012.GA21543@darkthrone.kvedulv.de>
	<20090603121307.GA15659@hades.panopticon>
	<20090603152810.GA21014@atarininja.org>
	<20090603160945.GC21014@atarininja.org>
	<20090603172033.GC27282@hades.panopticon>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090603172033.GC27282@hades.panopticon>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: Michael Moll <kvedulv@kvedulv.de>, bz@FreeBSD.org, jamie@FreeBSD.org,
	freebsd-current@freebsd.org
Subject: Re: Kernel panic when accessing ZFS-Filesystem via NFS
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 17:40:24 -0000

On Wed, Jun 03, 2009 at 09:20:33PM +0400, Dmitry Marakasov wrote:
> * Wesley Shields (wxs@FreeBSD.org) wrote:
> 
> Well, cred->cr_prison was the only thing to panic on in prison_priv_check,
> so that was obvious without the backtrace. I'll try to addd checking
> for null pointer here for now (as I'm more concerned in bringing
> my NAS back up).

Adding a check for null to jailed() in kern_jail.c will most likely work
around the problem, but I was under the impression that cred->cr_prison
should be &prison0 and never null with the new way of doing things. I'd
still like to know why cr_prison is null.

Of course, I have no idea what the implications of a null check in
jailed() will be outside of this one scenario.

-- WXS