From: Eryu Guan <guaneryu@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
linux-ext4@vger.kernel.org
Subject: Re: Testing Ext4 encryption with fstests
Date: Sun, 3 Dec 2017 14:22:10 +0800 [thread overview]
Message-ID: <20171203062210.GA2775@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20171203024449.foyydafswblqceou@thunk.org>
Hi Ted,
On Sat, Dec 02, 2017 at 09:44:49PM -0500, Theodore Ts'o wrote:
> On Sat, Dec 02, 2017 at 08:44:29AM +0530, Chandan Rajendra wrote:
...
>
> generic/466 and generic/468 are new tests that are failing on the
> standard 4k config as well as the encrypt case. On my todo list to
> look at more closely and triage.
I've sent a patch to fix generic/468 failure on Nov. 15th, would you
please take a look and review it?
ext4: fix fdatasync(2) after fallocate(2) operation
https://patchwork.ozlabs.org/patch/838141/
Thanks,
Eryu
prev parent reply other threads:[~2017-12-03 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 3:14 Testing Ext4 encryption with fstests Chandan Rajendra
2017-12-03 2:44 ` Theodore Ts'o
2017-12-03 6:22 ` Eryu Guan [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=20171203062210.GA2775@eguan.usersys.redhat.com \
--to=guaneryu@gmail.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).