From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Daniel Vacek <neelx@suse.com>, David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, Josef Bacik <josef@toxicpanda.com>,
Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: Re: [PATCH 0/8] btrfs-progs: fscrypt updates
Date: Thu, 16 Oct 2025 07:40:45 +1030 [thread overview]
Message-ID: <84dabbbd-1b7b-4d51-b585-d3dcad3fd88f@gmx.com> (raw)
In-Reply-To: <20251015121157.1348124-1-neelx@suse.com>
在 2025/10/15 22:41, Daniel Vacek 写道:
> This series is a rebase of an older set of fscrypt related changes from
> Sweet Tea Dorminy and Josef Bacik found here:
> https://github.com/josefbacik/btrfs-progs/tree/fscrypt
I'm wondering if encryption (fscrypt) for btrfs is still being pushed.
IIRC meta has given up the effort to push for this feature.
Thanks,
Qu
>
> The only difference is dropping of commit 56b7131 ("btrfs-progs: escape
> unprintable characters in names") and a bit of code style changes.
>
> The mentioned commit is no longer needed as a similar change was already
> merged with commit ef7319362 ("btrfs-progs: dump-tree: escape special
> characters in paths or xattrs").
>
> I just had to add one trivial fixup so that the fstests could parse the
> output correctly.
>
> Daniel Vacek (1):
> btrfs-progs: string-utils: do not escape space while printing
>
> Josef Bacik (1):
> btrfs-progs: check: fix max inline extent size
>
> Sweet Tea Dorminy (6):
> btrfs-progs: add new FEATURE_INCOMPAT_ENCRYPT flag
> btrfs-progs: start tracking extent encryption context info
> btrfs-progs: add inode encryption contexts
> btrfs-progs: interpret encrypted file extents.
> btrfs-progs: handle fscrypt context items
> btrfs-progs: check: update inline extent length checking
>
> check/main.c | 36 ++++++++++--------
> common/string-utils.c | 1 -
> kernel-shared/accessors.h | 43 ++++++++++++++++++++++
> kernel-shared/ctree.h | 3 +-
> kernel-shared/print-tree.c | 41 +++++++++++++++++++++
> kernel-shared/tree-checker.c | 65 +++++++++++++++++++++++++++------
> kernel-shared/uapi/btrfs.h | 1 +
> kernel-shared/uapi/btrfs_tree.h | 27 +++++++++++++-
> 8 files changed, 186 insertions(+), 31 deletions(-)
>
next prev parent reply other threads:[~2025-10-15 21:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 12:11 [PATCH 0/8] btrfs-progs: fscrypt updates Daniel Vacek
2025-10-15 12:11 ` [PATCH 1/8] btrfs-progs: check: fix max inline extent size Daniel Vacek
2025-10-15 12:11 ` [PATCH 2/8] btrfs-progs: add new FEATURE_INCOMPAT_ENCRYPT flag Daniel Vacek
2025-10-24 21:16 ` David Sterba
2025-10-15 12:11 ` [PATCH 3/8] btrfs-progs: start tracking extent encryption context info Daniel Vacek
2025-10-24 21:29 ` David Sterba
2025-10-24 22:43 ` Qu Wenruo
2025-11-05 8:28 ` Daniel Vacek
2025-11-05 8:22 ` Daniel Vacek
2025-11-05 8:27 ` Daniel Vacek
2025-11-05 9:12 ` Qu Wenruo
2025-11-05 10:55 ` Daniel Vacek
2025-11-26 14:11 ` David Sterba
2025-11-27 8:40 ` Daniel Vacek
2025-10-15 12:11 ` [PATCH 4/8] btrfs-progs: add inode encryption contexts Daniel Vacek
2025-10-15 12:11 ` [PATCH 5/8] btrfs-progs: interpret encrypted file extents Daniel Vacek
2025-11-02 22:26 ` Qu Wenruo
2025-11-03 9:57 ` Daniel Vacek
2025-11-05 7:46 ` Daniel Vacek
2025-10-15 12:11 ` [PATCH 6/8] btrfs-progs: handle fscrypt context items Daniel Vacek
2025-10-15 12:11 ` [PATCH 7/8] btrfs-progs: check: update inline extent length checking Daniel Vacek
2025-10-15 12:11 ` [PATCH 8/8] btrfs-progs: string-utils: do not escape space while printing Daniel Vacek
2025-10-17 16:43 ` David Sterba
2025-10-18 17:50 ` Daniel Vacek
2025-10-15 21:10 ` Qu Wenruo [this message]
2025-10-15 21:19 ` [PATCH 0/8] btrfs-progs: fscrypt updates Daniel Vacek
2025-10-15 21:20 ` Qu Wenruo
2025-10-16 15:16 ` Johannes Thumshirn
2025-10-17 20:54 ` Mark Harmstone
2025-10-24 21:10 ` David Sterba
2025-10-17 16:45 ` David Sterba
2025-10-18 18:01 ` Daniel Vacek
2025-11-04 14:56 ` David Sterba
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=84dabbbd-1b7b-4d51-b585-d3dcad3fd88f@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=neelx@suse.com \
--cc=sweettea-kernel@dorminy.me \
/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).