From: Theodore Ts'o <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: more resize breakage
Date: Thu, 29 May 2014 02:09:02 -0400 [thread overview]
Message-ID: <20140529060902.GC25041@thunk.org> (raw)
In-Reply-To: <20140529060048.GB27499@birch.djwong.org>
Darrick,
I don't think the problem which Eric reported in the head of this
thread is fixed by one of your patches, but you did send some patches
which I think would fix some resize bugs, which are setting on the
ext4 "dev" branch for the next merge window.
It's too late for me to deal with this tonight, but I'll run a quick
check and see if Eric's repro fails with the tip of the ext4 patch
queue.
Eric, thanks for creating this tool; I think it will incredibly
helpful in terms of finding and fixing some of these edge cases.
Cheers,
- Ted
prev parent reply other threads:[~2014-05-29 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 5:22 more resize breakage Eric Sandeen
2014-05-29 5:27 ` Darrick J. Wong
2014-05-29 5:29 ` Eric Sandeen
2014-05-29 6:00 ` Darrick J. Wong
2014-05-29 6:09 ` Theodore Ts'o [this message]
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=20140529060902.GC25041@thunk.org \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).