From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: [RFC] The many faces of the I_LOCK Date: Thu, 22 Feb 2007 11:40:23 +0000 Message-ID: <20070222114023.GA7149@lazybastard.org> References: <20070221130956.GB464@lazybastard.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Anton Altaparmakov , David Chinner , Dave Kleikamp , Al Viro , Christoph Hellwig To: linux-fsdevel@vger.kernel.org Return-path: Received: from lazybastard.de ([212.112.238.170]:45524 "EHLO longford.lazybastard.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933032AbXBVLnu (ORCPT ); Thu, 22 Feb 2007 06:43:50 -0500 Content-Disposition: inline In-Reply-To: <20070221130956.GB464@lazybastard.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 21 February 2007 13:09:56 +0000, J=C3=B6rn Engel wrote: >=20 > 3. Seperating out sync notification Ok, that turned out to be a bad idea. Deadlock still exists. Now it i= s harder to hit and involves: I_SYNC waiting on LogFS write mutex clear_inode waiting on I_SYNC with I_FREEING set find_inode waiting for I_FREEING LogFS write path waiting for find_inode Sorry for the noise. J=C3=B6rn --=20 Rules of Optimization: Rule 1: Don't do it. Rule 2 (for experts only): Don't do it yet. -- M.A. Jackson - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html