From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Re: [BUG] xfstests #68 with data=journal hang against 3.8-rc7 and 'dev' branch
Date: Mon, 18 Feb 2013 00:04:22 -0500 [thread overview]
Message-ID: <20130218050422.GD10361@thunk.org> (raw)
In-Reply-To: <20130217172208.GB4059@gmail.com>
On Mon, Feb 18, 2013 at 01:22:08AM +0800, Zheng Liu wrote:
> Hi all,
>
> Xfstests #68 will hang with data=journal in 3.8-rc7 and 'dev' branch. I
> remember that there has a patch for ext4 to fix filesystem freeze bug
> but I am not sure whether it can fix this bug and it has been applied
> into 'dev' branch. So I file this bug here.
Hmm.... I have never seen this test fail with my tests (although I'm
just using the dev branch; I have not tried merging in 3.8-rc7 into
the dev branch for any of my tests).
Is it failing for you reliably?
The commit which I think you are referring to fixed a bug where a user
was trying to freeze a file systme which was mounted over a FUSE
partition. It's certainly in dev; it's not marked for inclusion for
the stable patch series since it's an optimization change, and it was
not intended to fix something which is inherently dangerous (and if it
works, it's purely by luck, since the FUSE userspace will get frozen
before the file system is necessarily done doing its journal freeze
operation; the change may have affected the timing so that the user
would get lucky, but it's a sheer chance thing, and there's no
guarantee the user will lose later).
- Ted
next prev parent reply other threads:[~2013-02-18 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 17:22 [BUG] xfstests #68 with data=journal hang against 3.8-rc7 and 'dev' branch Zheng Liu
2013-02-18 5:04 ` Theodore Ts'o [this message]
2013-02-18 17:33 ` Zheng Liu
2013-02-19 19:57 ` Eric Whitney
2013-02-19 8:55 ` Jan Kara
2013-02-22 19:46 ` Theodore Ts'o
2013-02-26 18:49 ` Jan Kara
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=20130218050422.GD10361@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
/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).