Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756556AbYGINaQ (ORCPT ); Wed, 9 Jul 2008 09:30:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753413AbYGINaA (ORCPT ); Wed, 9 Jul 2008 09:30:00 -0400 Received: from orchid.cbk.poznan.pl ([150.254.183.30]:4031 "EHLO orchid.cbk.poznan.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753330AbYGIN36 (ORCPT ); Wed, 9 Jul 2008 09:29:58 -0400 X-Greylist: delayed 1769 seconds by postgrey-1.27 at vger.kernel.org; Wed, 09 Jul 2008 09:29:58 EDT Subject: Re: [PATCH 3/3] Add timeout feature From: Olaf =?iso-8859-2?Q?Fr=B1czyk?= To: Theodore Tso Cc: Arjan van de Ven , Miklos Szeredi , hch@infradead.org, pavel@suse.cz, t-sato@yk.jp.nec.com, akpm@linux-foundation.org, viro@ZenIV.linux.org.uk, linux-ext4@vger.kernel.org, xfs@oss.sgi.com, dm-devel@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, axboe@kernel.dk, mtk.manpages@googlemail.com In-Reply-To: <20080709122401.GK9957@mit.edu> References: <20080709010922.GE9957@mit.edu> <20080709061621.GA5260@infradead.org> <20080708234120.5072111f@infradead.org> <20080708235502.1c52a586@infradead.org> <20080709071346.GS11558@disturbed> <20080709110900.GI9957@mit.edu> <20080709114958.GV11558@disturbed> <20080709122401.GK9957@mit.edu> Content-Type: text/plain; charset=UTF-8 Date: Wed, 09 Jul 2008 14:59:20 +0200 Message-Id: <1215608360.20914.14.camel@venus.local.navi.pl> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1096 Lines: 27 On Wed, 2008-07-09 at 08:24 -0400, Theodore Tso wrote: > On Wed, Jul 09, 2008 at 09:49:58PM +1000, Dave Chinner wrote: > > (e) none of the above. The kernel compilation will appear to pause > > until the filesystem is unfrozen. No other visible effect should > > occur. It will get blocked in a write or filesystem transaction > > because the fs is frozen. > > So if the process which froze the filesystem accidentally tries > writing to a log file (or database file containing the backup > information, or whatever) that happens to be on the filesystem that is > frozen, that process will get blocked and you end up in a deadlock; > did I get that right? Where do you see the deadlock? The process doesn't have a lock on filesystem or something. You can always unfreeze from another process. Regards, Olaf -- Olaf Frączyk -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/