linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Greg Freemyer <greg.freemyer@gmail.com>,
	Masayoshi MIZUMA <m.mizuma@jp.fujitsu.com>,
	Jan Kara <jack@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [BUG] ext3: cannot unfreeze a filesystem due to a deadlock
Date: Wed, 07 Sep 2011 12:10:07 -0500	[thread overview]
Message-ID: <4E67A56F.8040403@redhat.com> (raw)
In-Reply-To: <20110907165017.GA19151@infradead.org>

On 9/7/11 11:50 AM, Christoph Hellwig wrote:
> On Wed, Sep 07, 2011 at 12:45:34PM -0400, Greg Freemyer wrote:
>>> Can you add this testcase to xfstests?
>>
>> Christoph,
>>
>> Isn't that just a matter of extending test 068 to ext4
> 
> If you have recent enough xfsprogs that allow the freeze command
> for foreign filesystems that might work. 

where "recent enough" is since Tue Feb 10 14:41:51 2009 -0600

I say go for it :)

Could always add a quick helper to make sure the xfs_io command
doesn't fail on freeze, and _notrun if it does.

-Eric


  reply	other threads:[~2011-09-07 17:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  3:29 [BUG] ext3: cannot unfreeze a filesystem due to a deadlock Masayoshi MIZUMA
2011-09-07  6:40 ` Christoph Hellwig
2011-09-07  7:23   ` Masayoshi MIZUMA
2011-09-07 16:45   ` Greg Freemyer
2011-09-07 16:50     ` Christoph Hellwig
2011-09-07 17:10       ` Eric Sandeen [this message]
2011-09-07 17:17         ` Christoph Hellwig
2011-09-07 17:34 ` Jan Kara
2011-09-07 17:56   ` Greg Freemyer
2011-09-07 22:32     ` Jan Kara
2011-09-09  3:05       ` Greg Freemyer
2011-09-13  3:00   ` Valerie Aurora
2011-09-14  6:24     ` Masayoshi MIZUMA

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=4E67A56F.8040403@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=greg.freemyer@gmail.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=m.mizuma@jp.fujitsu.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).