From: "Richard W.M. Jones" <rjones@redhat.com>
To: Torsten Hilbrich <torsten.hilbrich@secunet.com>
Cc: jmoyer@redhat.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:34:57 +0100 [thread overview]
Message-ID: <20120625113457.GA1289@amd.home.annexia.org> (raw)
In-Reply-To: <4FDEC3C2.4060909@secunet.com>
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.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.
http://et.redhat.com/~rjones/virt-p2v
next prev parent reply other threads:[~2012-06-25 11:35 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 [this message]
2012-06-25 16:38 ` Jeff Moyer
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=20120625113457.GA1289@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).