From owner-freebsd-hackers Tue Jan 5 18:07:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25016 for freebsd-hackers-outgoing; Tue, 5 Jan 1999 18:07:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25011 for ; Tue, 5 Jan 1999 18:07:21 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA10884 for ; Wed, 6 Jan 1999 12:36:25 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA84036 for hackers@freebsd.org; Wed, 6 Jan 1999 12:36:28 +1030 (CST) Date: Wed, 6 Jan 1999 12:36:28 +1030 From: Greg Lehey To: FreeBSD Hackers Subject: Unlocking vnodes from different processes Message-ID: <19990106123627.N78349@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Vinum, I sometimes need to lock a vnode in one process and unlock it in another. Since 3.0, I've been getting panics when I do this: panicstr: lockmgr: pid 429, not exclusive lock holder 428 unlocking Can I assume that the other parameters (flag, p) to VOP_UNLOCK will enable me to do this anyway? Also, since I don't perform the lock directly (it happens as a side-effect of opening the vnode), is there a kosher way to find out what process locked the vnode? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message