From dsh@neva.vlink.ru  Tue Feb  8 08:45:18 2005
Return-Path: <dsh@neva.vlink.ru>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3F5DF16A4CE; Tue,  8 Feb 2005 08:45:18 +0000 (GMT)
Received: from deliver.smtp.vlink.ru (alias.rigel.internal.vlink.ru [217.23.88.17])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9300B43D49; Tue,  8 Feb 2005 08:45:17 +0000 (GMT)
	(envelope-from dsh@neva.vlink.ru)
Received: from smtp.smtp.vlink.ru (clamav.smtp.vlink.ru [192.168.4.1])
	by deliver.smtp.vlink.ru (Postfix) with ESMTP id 63A4D45328;
	Tue,  8 Feb 2005 11:45:16 +0300 (MSK)
Received: from neva.vlink.ru (neva.vlink.ru [217.107.252.29])
	by smtp.smtp.vlink.ru (Postfix) with ESMTP id 1E5AB45104;
	Tue,  8 Feb 2005 11:45:16 +0300 (MSK)
Received: from neva.vlink.ru (localhost [127.0.0.1])
	by neva.vlink.ru (8.13.1/8.13.1) with ESMTP id j188jFku000712;
	Tue, 8 Feb 2005 11:45:15 +0300 (MSK)
	(envelope-from dsh@neva.vlink.ru)
Received: (from dsh@localhost)
	by neva.vlink.ru (8.13.1/8.13.1/Submit) id j188jFPQ000708;
	Tue, 8 Feb 2005 11:45:15 +0300 (MSK)
	(envelope-from dsh)
Message-Id: <200502080845.j188jFPQ000708@neva.vlink.ru>
Date: Tue, 8 Feb 2005 11:45:15 +0300 (MSK)
From: Denis Shaposhnikov <dsh@vlink.ru>
Reply-To: Denis Shaposhnikov <dsh@vlink.ru>
To: FreeBSD-gnats-submit@freebsd.org
Cc: dsh@neva.vlink.ru, phk@freebsd.org
Subject: kernel panic on jail with unionfs
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         77251
>Category:       kern
>Synopsis:       kernel panic on jail with unionfs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    phk
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 08 08:50:22 GMT 2005
>Closed-Date:    Wed May 04 18:26:51 GMT 2005
>Last-Modified:  Wed May 04 18:26:51 GMT 2005
>Originator:     Denis Shaposhnikov
>Release:        FreeBSD 6.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD neva.vlink.ru 6.0-CURRENT FreeBSD 6.0-CURRENT #8: Mon Feb 7 09:49:25 MSK 2005 dsh@neva.vlink.ru:/var/FreeBSD/obj/var/FreeBSD/src/sys/NEVA i386

>Description:

Using jail on unionfs inside make kernel panic.

>How-To-Repeat:

# mount_unionfs -r -o ro /rescue /mnt
# jail /mnt unionfs.test 127.0.0.1 /tcsh

"Panic: page fault" here.

>Fix:
>Release-Note:
>Audit-Trail:
Adding to audit trail from misfiled PR 77252:

From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>

 Please try to get me a kernel traceback if possible.
 
 What is the underlying filesystem type ?

From: Maxim Konovalov <maxim@macomnet.ru>
To: phk@freebsd.org
Cc: bug-followup@freebsd.org
Subject: Re: kern/77251: kernel panic on jail with unionfs
Date: Tue, 8 Feb 2005 21:49:18 +0300 (MSK)

 kgdb produces an incorrect stack trace so from the memory:
 
 exec_map_first_page()+0x35
 do_execve()
 kern_execve()
 syscall()
 
 The underlying FS is UFS2.
 
 -- 
 Maxim Konovalov
State-Changed-From-To: open->closed 
State-Changed-By: kris 
State-Changed-When: Wed Feb 9 04:25:10 GMT 2005 
State-Changed-Why:  
unionfs is documented to be broken; see the manpage.  A number of 
existing PRs contain specific panic conditions with additional 
debugging information in case a future developer becomes interested in 
trying to fix this, but this PR does not contain enough information to 
be even that useful. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=77251 
State-Changed-From-To: closed->open 
State-Changed-By: kris 
State-Changed-When: Wed Feb 9 04:43:59 GMT 2005 
State-Changed-Why:  
Reopen and assign to phk since it seems to be a recent regression. 


Responsible-Changed-From-To: freebsd-bugs->phk 
Responsible-Changed-By: kris 
Responsible-Changed-When: Wed Feb 9 04:43:59 GMT 2005 
Responsible-Changed-Why:  
Reopen and assign to phk since it seems to be a recent regression. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=77251 

From: Maxim Konovalov <maxim@macomnet.ru>
To: Kris Kennaway <kris@freebsd.org>
Cc: dsh@vlink.ru, bug-followup@freebsd.org, phk@freebsd.org
Subject: Re: kern/77251: kernel panic on jail with unionfs
Date: Wed, 9 Feb 2005 07:42:27 +0300 (MSK)

 On Wed, 9 Feb 2005, 04:26-0000, Kris Kennaway wrote:
 
 > Synopsis: kernel panic on jail with unionfs
 >
 > State-Changed-From-To: open->closed
 > State-Changed-By: kris
 > State-Changed-When: Wed Feb 9 04:25:10 GMT 2005
 > State-Changed-Why:
 > unionfs is documented to be broken; see the manpage.  A number of
 > existing PRs contain specific panic conditions with additional
 > debugging information in case a future developer becomes interested in
 > trying to fix this, but this PR does not contain enough information to
 > be even that useful.
 
 I am disagree.  It does contain 100% reproductable How-To-Repeate
 steps and FreeBSD does not allow to get more infomation (broken stack
 trace).  This particular setup used to work on RELENG_4 and on
 RELENG_5 and even RELENG_6.  This panic is a recent regression.
 Moreover, phk@ expressed interest.
 
 -- 
 Maxim Konovalov

From: Kris Kennaway <kris@obsecurity.org>
To: Maxim Konovalov <maxim@macomnet.ru>
Cc: Kris Kennaway <kris@freebsd.org>, dsh@vlink.ru,
	bug-followup@freebsd.org, phk@freebsd.org
Subject: Re: kern/77251: kernel panic on jail with unionfs
Date: Tue, 8 Feb 2005 20:44:44 -0800

 --1yeeQ81UyVL57Vl7
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Wed, Feb 09, 2005 at 07:42:27AM +0300, Maxim Konovalov wrote:
 > On Wed, 9 Feb 2005, 04:26-0000, Kris Kennaway wrote:
 >=20
 > > Synopsis: kernel panic on jail with unionfs
 > >
 > > State-Changed-From-To: open->closed
 > > State-Changed-By: kris
 > > State-Changed-When: Wed Feb 9 04:25:10 GMT 2005
 > > State-Changed-Why:
 > > unionfs is documented to be broken; see the manpage.  A number of
 > > existing PRs contain specific panic conditions with additional
 > > debugging information in case a future developer becomes interested in
 > > trying to fix this, but this PR does not contain enough information to
 > > be even that useful.
 >=20
 > I am disagree.  It does contain 100% reproductable How-To-Repeate
 > steps and FreeBSD does not allow to get more infomation (broken stack
 > trace).  This particular setup used to work on RELENG_4 and on
 > RELENG_5 and even RELENG_6.  This panic is a recent regression.
 > Moreover, phk@ expressed interest.
 
 OK, that wasn't clear from the text.
 
 kris
 
 --1yeeQ81UyVL57Vl7
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.0 (FreeBSD)
 
 iD8DBQFCCZU8Wry0BWjoQKURAsNpAJ9UIOUqwZePW5nVLGNqN+dKY1QLewCcDxS6
 Kx5gUGLBAmsP60GtASCna/U=
 =8bE5
 -----END PGP SIGNATURE-----
 
 --1yeeQ81UyVL57Vl7--
State-Changed-From-To: open->closed 
State-Changed-By: maxim 
State-Changed-When: Wed May 4 18:25:42 GMT 2005 
State-Changed-Why:  
Jeff has committed the fix for this bug in rev. 1.132 
sys/fs/unionfs/union_vnops.c. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=77251 
>Unformatted:
