From: Christoph Hellwig <hch@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-xfs@vger.kernel.org, zlang@redhat.com, djwong@kernel.org,
Daniel Vacek <neelx@suse.com>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-fscrypt@vger.kernel.org, David Sterba <dsterba@suse.com>,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 00/12] fstests: introduce fscrypt support for btrfs
Date: Mon, 27 Jul 2026 23:04:56 -0700 [thread overview]
Message-ID: <amhGiIsvNIni_VAE@infradead.org> (raw)
In-Reply-To: <20260728054847.GB99797@sol>
On Mon, Jul 27, 2026 at 10:48:47PM -0700, Eric Biggers wrote:
> Please keep sending out the tests along with the kernel patches. But
> yes, they aren't for immediate merging and should be tagged with RFC,
> and the cover letter should mention that the kernel patches are pending.
> Thanks!
I think the split of the v1 vs v2 policy tests might actually be useful
as-is now, but I'll defer to you.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Daniel Vacek <neelx@suse.com>,
Christoph Hellwig <hch@infradead.org>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, zlang@redhat.com,
djwong@kernel.org, David Sterba <dsterba@suse.com>,
linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH 00/12] fstests: introduce fscrypt support for btrfs
Date: Mon, 27 Jul 2026 23:04:56 -0700 [thread overview]
Message-ID: <amhGiIsvNIni_VAE@infradead.org> (raw)
In-Reply-To: <20260728054847.GB99797@sol>
On Mon, Jul 27, 2026 at 10:48:47PM -0700, Eric Biggers wrote:
> Please keep sending out the tests along with the kernel patches. But
> yes, they aren't for immediate merging and should be tagged with RFC,
> and the cover letter should mention that the kernel patches are pending.
> Thanks!
I think the split of the v1 vs v2 policy tests might actually be useful
as-is now, but I'll defer to you.
next prev parent reply other threads:[~2026-07-28 6:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 13:33 [PATCH 00/12] fstests: introduce fscrypt support for btrfs Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 01/12] common/encrypt: separate data and inode nonces Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 02/12] common/encrypt: add btrfs to get_encryption_*nonce Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 03/12] common/encrypt: add btrfs to get_ciphertext_filename Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 04/12] common/encrypt: enable making a encrypted btrfs filesystem Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 05/12] common/verity: explicitly don't allow btrfs encryption Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 06/12] btrfs: add simple test of reflink of encrypted data Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 07/12] btrfs: test snapshotting encrypted subvol Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 08/12] fstests: properly test for v1 encryption policies in encrypt tests Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 09/12] fstests: split generic/580 into two tests Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 10/12] fstests: split generic/581 " Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 11/12] fstests: split generic/613 " Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [PATCH 12/12] fscrypt-crypt-util: add support for per extent KDF Daniel Vacek
2026-07-24 13:33 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-28 3:19 ` [PATCH 00/12] fstests: introduce fscrypt support for btrfs Christoph Hellwig
2026-07-28 3:19 ` [f2fs-dev] " Christoph Hellwig
2026-07-28 5:44 ` Daniel Vacek
2026-07-28 5:44 ` [f2fs-dev] " Daniel Vacek via Linux-f2fs-devel
2026-07-28 5:48 ` Eric Biggers via Linux-f2fs-devel
2026-07-28 5:48 ` Eric Biggers
2026-07-28 6:04 ` Christoph Hellwig [this message]
2026-07-28 6:04 ` Christoph Hellwig
2026-07-28 6:07 ` Eric Biggers
2026-07-28 6:07 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
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=amhGiIsvNIni_VAE@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=neelx@suse.com \
--cc=zlang@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 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.