Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 14 Dec 2001 16:26:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 14 Dec 2001 16:26:01 -0500 Received: from monrovia-23.budapest.interware.hu ([195.70.53.215]:10756 "EHLO iluvatar.ath.cx") by vger.kernel.org with ESMTP id ; Fri, 14 Dec 2001 16:25:32 -0500 Date: Fri, 14 Dec 2001 22:24:12 +0100 Message-ID: <83heqtmr5v.wl@iluvatar.ath.cx> From: Gergely Nagy To: linux-kernel@vger.kernel.org Subject: Another loop bug? (Was: 2.4.17rc1aa1) In-Reply-To: <20011214181444.B2431@athlon.random> In-Reply-To: <20011214181444.B2431@athlon.random> User-Agent: Wanderlust/2.7.7 (Too Funky) Emacs/21.1 Mule/5.0 (SAKAKI) Organization: The MadHouse Project X-Marvin: Life, loathe it or ignore it, you can't like it. MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Only in 2.4.17rc1aa1: 00_loop-deadlock-1 > > Fixed loop deadlock (balance_dirty() must not be called within the > request_fn or it can deadlock or recurse way too much). It is > enough to recall balance_dirty() at the highest layer so this won't > introduce any stability problem. > Maybe my problem is unrelated to this, but when I try to mount an ext2 image (from an ext3 filesystem, if that counts), loop0 starts to eat CPU, and brings up the load to around 2.90. After a short time (about a minute after mounting the image), everything that tries to access the mounted area hangs. I can't umount it, and can't kill the processes which are trying to access it. I have this problem since 2.4.16, 2.4.14 (with ext3 0.9.15) works fine. - 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/