linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Satya Tangirala <satyat@google.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
	linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [xfstests-bld PATCH] test-appliance: exclude generic/587 from the encrypt tests
Date: Thu, 9 Jul 2020 11:41:45 -0700	[thread overview]
Message-ID: <20200709184145.GA3855682@gmail.com> (raw)
In-Reply-To: <20200709183701.2564213-1-satyat@google.com>

On Thu, Jul 09, 2020 at 06:37:01PM +0000, Satya Tangirala wrote:
> The encryption feature doesn't play well with quota, and generic/587
> tests quota functionality.
> 
> Signed-off-by: Satya Tangirala <satyat@google.com>
> ---
>  .../test-appliance/files/root/fs/ext4/cfg/encrypt.exclude        | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude
> index 47c26e7..07111c2 100644
> --- a/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude
> +++ b/kvm-xfstests/test-appliance/files/root/fs/ext4/cfg/encrypt.exclude
> @@ -24,6 +24,7 @@ generic/270
>  generic/381
>  generic/382
>  generic/566
> +generic/587
>  
>  # encryption doesn't play well with casefold (at least not yet)
>  generic/556
> -- 

Can you update encrypt_1k.exclude as well?

- Eric

  reply	other threads:[~2020-07-09 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 18:37 [xfstests-bld PATCH] test-appliance: exclude generic/587 from the encrypt tests Satya Tangirala
2020-07-09 18:41 ` Eric Biggers [this message]
2020-07-09 18:58   ` [xfstests-bld PATCH v2] " Satya Tangirala
2020-07-09 19:10     ` Eric Biggers
2020-09-01 16:17       ` Eric Biggers
2020-09-21 18:42         ` Eric Biggers
2020-09-24 17:27       ` Theodore Y. Ts'o
2020-09-28 22:06         ` Eric Biggers

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=20200709184145.GA3855682@gmail.com \
    --to=ebiggers@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=satyat@google.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 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).