From owner-freebsd-bugs@FreeBSD.ORG  Fri Oct  3 13:28:25 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C7CC6E0F
 for <freebsd-bugs@FreeBSD.org>; Fri,  3 Oct 2014 13:28:25 +0000 (UTC)
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 AF678CC9
 for <freebsd-bugs@FreeBSD.org>; Fri,  3 Oct 2014 13:28:25 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s93DSPWq065451
 for <freebsd-bugs@FreeBSD.org>; Fri, 3 Oct 2014 13:28:25 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 193803] zvol rename failing due to out of order locking
Date: Fri, 03 Oct 2014 13:28:25 +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.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: kash@tripleback.net
X-Bugzilla-Status: Issue Resolved
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-193803-8-NQUE9gTTUJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193803-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-193803-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Oct 2014 13:28:25 -0000

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

--- Comment #30 from kash@tripleback.net ---
(In reply to Steven Hartland from comment #28)
> So just to confirm, this does fix your deadlock issue?
> 
> For reference the current locking for zvol changes is actually quite
> specific to FreeBSD so not really an upstream issue.

Richard Yao was saying there's potential for converging the pathways still, ZoL
and Illumos have different ways of structuring locks, and thought the way this
was handled is a bit too similar to the Big Kernel Lock, but I don't know much
about this, I'm a less articulate coder.

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