From: Jeff Moyer <jmoyer@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Torsten Hilbrich <torsten.hilbrich@secunet.com>,
linux-ext4@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 3.3.8 breaks accidental ext3 mount of extended partition
Date: Mon, 25 Jun 2012 12:38:03 -0400 [thread overview]
Message-ID: <x49r4t3z6s4.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20120625113457.GA1289@amd.home.annexia.org> (Richard W. M. Jones's message of "Mon, 25 Jun 2012 12:34:57 +0100")
"Richard W.M. Jones" <rjones@redhat.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.
Cheers,
Jeff
diff --git a/fs/buffer.c b/fs/buffer.c
index 838a9cf..c7062c8 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -1036,6 +1036,9 @@ grow_buffers(struct block_device *bdev, sector_t block, int size)
static struct buffer_head *
__getblk_slow(struct block_device *bdev, sector_t block, int size)
{
+ int ret;
+ struct buffer_head *bh;
+
/* Size must be multiple of hard sectorsize */
if (unlikely(size & (bdev_logical_block_size(bdev)-1) ||
(size < 512 || size > PAGE_SIZE))) {
@@ -1048,20 +1051,21 @@ __getblk_slow(struct block_device *bdev, sector_t block, int size)
return NULL;
}
- for (;;) {
- struct buffer_head * bh;
- int ret;
+retry:
+ bh = __find_get_block(bdev, block, size);
+ if (bh)
+ return bh;
+ ret = grow_buffers(bdev, block, size);
+ if (ret == 0) {
+ free_more_memory();
+ goto retry;
+ } else if (ret > 0) {
bh = __find_get_block(bdev, block, size);
if (bh)
return bh;
-
- ret = grow_buffers(bdev, block, size);
- if (ret < 0)
- return NULL;
- if (ret == 0)
- free_more_memory();
}
+ return NULL;
}
/*
next prev parent reply other threads:[~2012-06-25 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 5:59 Kernel 3.3.8 breaks accidental ext3 mount of extended partition Torsten Hilbrich
2012-06-18 19:03 ` Jeff Moyer
2012-06-19 5:59 ` Torsten Hilbrich
2012-06-19 17:43 ` Jeff Moyer
2012-06-20 6:14 ` Torsten Hilbrich
2012-06-22 0:12 ` Jan Kara
2012-06-22 12:33 ` Jeff Moyer
2012-06-20 12:18 ` Marcos Mello
2012-06-25 11:34 ` Richard W.M. Jones
2012-06-25 16:38 ` Jeff Moyer [this message]
2012-06-25 16:58 ` Richard W.M. Jones
2012-06-25 19:32 ` Richard W.M. Jones
2012-06-25 20:04 ` Jeff Moyer
2012-06-26 6:07 ` Torsten Hilbrich
2012-06-26 13:02 ` Jeff Moyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x49r4t3z6s4.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjones@redhat.com \
--cc=torsten.hilbrich@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).