From: Eryu Guan <guaneryu@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
Liu Bo <obuil.liubo@gmail.com>,
fstests@vger.kernel.org
Subject: Re: [PATCH] ext4/034: adjust commit which fixes the problem tested by ext4/034
Date: Sat, 29 Dec 2018 13:08:46 +0800 [thread overview]
Message-ID: <20181229050846.GC21777@desktop> (raw)
In-Reply-To: <20181226160805.8987-1-tytso@mit.edu>
On Wed, Dec 26, 2018 at 11:08:05AM -0500, Theodore Ts'o wrote:
> Also add a requirment that fallocate and fiemap is supported.
> (Fallocate isn't the case when we are emulating ext3, for example.)
>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Cc: Liu Bo <obuil.liubo@gmail.com>
Patch looks good, but I assume you meant to send it to
fstests@vger.kernel.org not linux-fstests@mit.edu :)
Thanks,
Eryu
> ---
> tests/ext4/034 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tests/ext4/034 b/tests/ext4/034
> index 5c34d0d9..f9e4bfaf 100755
> --- a/tests/ext4/034
> +++ b/tests/ext4/034
> @@ -8,7 +8,7 @@
> # "-o dioread_nolock,nodelalloc" is used.
> #
> # The bug was fixed by commit
> -# "Ext4: fix ENOSPC when both quota and dioread_nolock are enabled"
> +# "ext4: make sure enough credits are reserved for dioread_nolock writes"
> #
> seq=`basename $0`
> seqres=$RESULT_DIR/$seq
> @@ -41,6 +41,8 @@ _supported_os Linux
> _require_scratch
> _require_quota
> _require_nobody
> +_require_xfs_io_command "falloc"
> +_require_xfs_io_command "fiemap"
> _require_xfs_io_command "syncfs"
>
> echo "Format and mount"
> --
> 2.19.1
>
next prev parent reply other threads:[~2018-12-29 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 16:08 [PATCH] ext4/034: adjust commit which fixes the problem tested by ext4/034 Theodore Ts'o
2018-12-29 5:08 ` Eryu Guan [this message]
2018-12-29 13:54 ` Theodore Y. Ts'o
2018-12-29 13:54 ` Theodore Y. Ts'o
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=20181229050846.GC21777@desktop \
--to=guaneryu@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=obuil.liubo@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.