From owner-freebsd-current Mon Aug 5 1:41:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 781C337B400 for ; Mon, 5 Aug 2002 01:41:56 -0700 (PDT) Received: from smtp2.enst.fr (matrix2.enst.fr [137.194.2.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CB6C43E65 for ; Mon, 5 Aug 2002 01:41:55 -0700 (PDT) (envelope-from beyssac@bofh.enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "bofh.enst.fr", Issuer CN "ENST CA" (verified OK)) by smtp2.enst.fr (Postfix) with ESMTP id 011F41EEA2 for ; Mon, 5 Aug 2002 10:41:53 +0200 (MEST) Received: from bofh.enst.fr (localhost [127.0.0.1]) by bofh.enst.fr (8.12.5/8.12.3) with ESMTP id g758frt4039670 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 5 Aug 2002 10:41:53 +0200 (CEST) (envelope-from beyssac@bofh.enst.fr) Received: (from beyssac@localhost) by bofh.enst.fr (8.12.5/8.12.3/Submit) id g758frgf039669 for freebsd-current@freebsd.org; Mon, 5 Aug 2002 10:41:53 +0200 (CEST) Date: Mon, 5 Aug 2002 10:41:53 +0200 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: deadlock in fs/msdosfs/msdosfs_vnops.c:msdosfs_fsync() Message-ID: <20020805104153.A37733@bofh.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm having a problem with the fsync() call on the MSDOS filesystem. I have a reproductible way (using a specific application under Wine) to get it to deadlock in the msleep() call. If I disable msdos_fsync() entirely by adding a return 0 at the top, everything runs smoothly, no deadlock. Since AFAIK the problem doesn't occur with ufs fsync(), should I suppose this may have to do (and should I start looking) with the way msdosfs handles vp->v_numoutput, can it be a deadlock with some other vnode locking in the msdosfs code, or can it be an unexpected side-effet of recent SMP/KSE changes (not likely considering my machine is UP) ? Any ideas or hints welcome on where I should start looking... -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message