From: Jeff Moyer Subject: Re: Kernel 3.3.8 breaks accidental ext3 mount of extended partition Date: Tue, 26 Jun 2012 09:02:27 -0400 Message-ID: References: <4FDEC3C2.4060909@secunet.com> <20120625113457.GA1289@amd.home.annexia.org> <4FE951A0.8040900@secunet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Richard W.M. Jones" , linux-ext4@vger.kernel.org, LKML To: Torsten Hilbrich Return-path: Received: from mx1.redhat.com ([209.132.183.28]:18763 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756430Ab2FZNCb (ORCPT ); Tue, 26 Jun 2012 09:02:31 -0400 In-Reply-To: <4FE951A0.8040900@secunet.com> (Torsten Hilbrich's message of "Tue, 26 Jun 2012 08:07:28 +0200") Sender: linux-ext4-owner@vger.kernel.org List-ID: Torsten Hilbrich writes: > Am 25.06.2012 18:38, schrieb Jeff Moyer: >> "Richard W.M. Jones" writes: >> >>> On Mon, Jun 18, 2012 at 07:59:30AM +0200, Torsten Hilbrich wrote: >>>> Hello, >>>> >>>> a software that tries to mount each existing partition as ext3 file system started to fail when updating from v3.3.7 to v3.3.8. >>>> >>>> The applications then hangs-up in the mount syscall, here is a snapshot of its stack at this moment: >>> >>> We just ran into what we think is the same problem. >>> >>> Note that ext4 fails like this for any 1024 byte sized filesystem (of >>> zeroes) that you try to mount. It's really nothing to do with >>> extended partitions. >>> >>> Here is a very simple reproducer + stack trace: >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=835019#c4 >>> >>> I will try out the patch suggested later on in this thread. >> >> Please try the attached patch instead. The patch I had originally >> posted for this allowed marking the first buffer beyond EOD as >> uptodate. This isn't correct. The patch I've attached below fixes the >> infinite loop in __getblk_slow. > > This patch also fixes the ext3 mount problem on extented partition. Great news, thanks for testing, guys! I'll follow up with another patch posting this morning. Cheers, Jeff