From: Theodore Ts'o <tytso@mit.edu>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
"Lukáš Czerner" <lczerner@redhat.com>
Subject: Re: [PATCH v2 2/2] ext4: disable COLLAPSE_RANGE for bigalloc
Date: Sat, 19 Apr 2014 18:12:21 -0400 [thread overview]
Message-ID: <20140419221221.GD13492@thunk.org> (raw)
In-Reply-To: <000d01cf5b8b$5b149110$113db330$@samsung.com>
On Sat, Apr 19, 2014 at 01:53:50PM +0900, Namjae Jeon wrote:
> From: Namjae Jeon <namjae.jeon@samsung.com>
>
> Once COLLAPSE RANGE is be disable for ext4 with bigalloc feature till finding
> root-cause of problem. It will be enable with fixing that regression of
> xfstest(generic 075 and 091) again.
>
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
> Signed-off-by: Ashish Sangwan <a.sangwan@samsung.com>
> Reviewed-by: Lukas Czerner <lczerner@redhat.com>
Thanks, applied.
What's the status of the "[2/3] ext4: fix ZERO_RANGE test failure in
data journalling mode" patch. Is it no longer needed?
- Ted
next prev parent reply other threads:[~2014-04-19 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 4:53 [PATCH v2 2/2] ext4: disable COLLAPSE_RANGE for bigalloc Namjae Jeon
2014-04-19 22:12 ` Theodore Ts'o [this message]
2014-04-21 4:52 ` Namjae Jeon
2014-04-21 13:31 ` Theodore Ts'o
2014-04-22 5:55 ` Namjae Jeon
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=20140419221221.GD13492@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=namjae.jeon@samsung.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