From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: interesting way to break ext3 using loop devices Date: Wed, 15 Nov 2006 10:40:48 -0500 Message-ID: <20061115154048.GA15611@thunk.org> References: <200611151536.21066.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org Return-path: Received: from THUNK.ORG ([69.25.196.29]:16839 "EHLO thunker.thunk.org") by vger.kernel.org with ESMTP id S1030585AbWKOPkw (ORCPT ); Wed, 15 Nov 2006 10:40:52 -0500 To: Andi Kleen Content-Disposition: inline In-Reply-To: <200611151536.21066.ak@suse.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Nov 15, 2006 at 03:36:20PM +0100, Andi Kleen wrote: > Of course this was clearly an operator error and > copying a file system into itself is clearly a sick thing > to do, but still it shouldn't cause symptoms like this. Perhaps > it points to a deeper issue. Agreed; I'm guessing it's a bug in the loop device at first glance. - Ted