From owner-freebsd-fs@freebsd.org  Tue Nov 10 06:24:40 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA746A2A929
 for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 10 Nov 2015 06:24:40 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D7F4114AA
 for <freebsd-fs@FreeBSD.org>; Tue, 10 Nov 2015 06:24:40 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAA6OegS047096
 for <freebsd-fs@FreeBSD.org>; Tue, 10 Nov 2015 06:24:40 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 201677] unionfs or tmpfs kernel panic
Date: Tue, 10 Nov 2015 06:24:40 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-BETA1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-201677-3630-c1oxUvvFq0@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201677-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-201677-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2015 06:24:41 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201677

--- Comment #3 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Franco Fichtner from comment #1)
tmpfs change is completely wrong, there is no reason for tmpfs vnode lock to be
recursive.  Unionfs is broken architecturally, it was so for the whole its
existence, which is cause of this backtrace and many other issues you could get
with the unionfs breaking all assumptions of VFS and filesystems.

-- 
You are receiving this mail because:
You are the assignee for the bug.