[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FE951A0.8040900@secunet.com>
Date: Tue, 26 Jun 2012 08:07:28 +0200
From: Torsten Hilbrich <torsten.hilbrich@...unet.com>
To: Jeff Moyer <jmoyer@...hat.com>
CC: "Richard W.M. Jones" <rjones@...hat.com>,
linux-ext4@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Kernel 3.3.8 breaks accidental ext3 mount of extended partition
Am 25.06.2012 18:38, schrieb Jeff Moyer:
> "Richard W.M. Jones" <rjones@...hat.com> 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.
Torsten
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists