From: Ted Ts'o <tytso@mit.edu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Allison Henderson <achender@linux.vnet.ibm.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: hang in xfstest 204 with dev branch
Date: Wed, 25 May 2011 17:31:17 -0400 [thread overview]
Message-ID: <20110525213117.GA9520@thunk.org> (raw)
In-Reply-To: <BANLkTik66Fj7_uHmjsL65j+5s3VQ1_VdoQ@mail.gmail.com>
On Wed, May 25, 2011 at 10:01:38PM +0300, Amir Goldstein wrote:
>
> When running xfstests with 4K blocksize, test 204 (Test out ENOSPC
> flushing on small filesystems)
> hangs in an interruptible sleep (I can release it with ctrl-C).
>
> git bisect points at commit fc0d5c38963ed655e974025c63290563c172038a
> ext4: add flag to ext4_has_free_blocks
> as the offender.
I found and fixed it. It was a bug I accidently introduced when I was
cleaning up that patches. Try the latest dev branch from the ext4.git
tree....
- Ted
next prev parent reply other threads:[~2011-05-25 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 19:01 hang in xfstest 204 with dev branch Amir Goldstein
2011-05-25 21:31 ` Ted Ts'o [this message]
2011-05-26 11:38 ` Amir Goldstein
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=20110525213117.GA9520@thunk.org \
--to=tytso@mit.edu \
--cc=achender@linux.vnet.ibm.com \
--cc=amir73il@gmail.com \
--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).