From owner-freebsd-fs@FreeBSD.ORG  Wed Jun  3 12:20:41 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7C736621
 for <freebsd-fs@FreeBSD.org>; Wed,  3 Jun 2015 12:20:41 +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 65C9914E4
 for <freebsd-fs@FreeBSD.org>; Wed,  3 Jun 2015 12:20:41 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t53CKfuv097077
 for <freebsd-fs@FreeBSD.org>; Wed, 3 Jun 2015 12:20:41 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 200585] [nlm] Fatal trap 9 when printing out KASSERT trying to
 run umount -f on an NFS share while it's trying to print out "lockd not
 responding" in nlm(4)
Date: Wed, 03 Jun 2015 12:20:41 +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: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: rmacklem@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-200585-3630-Ju29VfsdYP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200585-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-200585-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: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2015 12:20:41 -0000

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

--- Comment #7 from Rick Macklem <rmacklem@FreeBSD.org> ---
It's been a while since I looked at it, but I
remember that there is a known issue with the
client side NLM for "umount -f". Basically it
unlocks and later relocks the vnode without
holding a refcnt on the mount point. At the time,
I didn't know enough about the mount point refcnt
stuff to fix it.

I'll try and take a look later to-day.

I don't know if this is the cause of the crash
(I can't remember what credentials are used), but
it does need to be fixed for "umount -f" to be safe
when running rpc.lockd. (I keep hoping people will
stop using rpc.lockd and rpc.statd, but it's just
a dream;-)

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