From: Christoph Hellwig <hch@infradead.org>
To: Daniel Vacek <neelx@suse.com>
Cc: hch@infradead.org, djwong@kernel.org, zlang@redhat.com,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.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 20:19:22 -0700 [thread overview]
Message-ID: <amgfuk12imPN2XJe@infradead.org> (raw)
In-Reply-To: <20260724133328.1837318-1-neelx@suse.com>
On Fri, Jul 24, 2026 at 03:33:16PM +0200, Daniel Vacek wrote:
> This is a rebase and cleanup of older patches [0] from Sweet Tea and Josef
> fixed to work with the recent kernel and btrfs-progs changes.
I'm not sure if you post this just for reference or what the intent here
is, especially with a cover letter like this that doesn't have much
information.
Before we doing anything for the btrfs-specific fscrypt changes in
xfstests, those changes should be accepted upstream first.
Maybe some thing like splitting tests might make sense without that,
but then it should be posted separately.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-07-28 3:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 13:33 [f2fs-dev] [PATCH 00/12] fstests: introduce fscrypt support for btrfs Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 01/12] common/encrypt: separate data and inode nonces Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 02/12] common/encrypt: add btrfs to get_encryption_*nonce Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 03/12] common/encrypt: add btrfs to get_ciphertext_filename Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 04/12] common/encrypt: enable making a encrypted btrfs filesystem Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 05/12] common/verity: explicitly don't allow btrfs encryption Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 06/12] btrfs: add simple test of reflink of encrypted data Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 07/12] btrfs: test snapshotting encrypted subvol Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 08/12] fstests: properly test for v1 encryption policies in encrypt tests Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 09/12] fstests: split generic/580 into two tests Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 10/12] fstests: split generic/581 " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 11/12] fstests: split generic/613 " Daniel Vacek via Linux-f2fs-devel
2026-07-24 13:33 ` [f2fs-dev] [PATCH 12/12] fscrypt-crypt-util: add support for per extent KDF Daniel Vacek via Linux-f2fs-devel
2026-07-28 3:19 ` Christoph Hellwig [this message]
2026-07-28 5:44 ` [f2fs-dev] [PATCH 00/12] fstests: introduce fscrypt support for btrfs Daniel Vacek via Linux-f2fs-devel
2026-07-28 5:48 ` Eric Biggers via Linux-f2fs-devel
2026-07-28 6:04 ` Christoph Hellwig
2026-07-28 6:07 ` 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=amgfuk12imPN2XJe@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox