Linux FSCRYPT development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Daniel Vacek <neelx@suse.com>, David Sterba <dsterba@suse.com>
Cc: linux-fscrypt@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/7] btrfs-progs: fscrypt updates
Date: Wed, 8 Jul 2026 14:29:55 +0930	[thread overview]
Message-ID: <b7861828-64d1-4fef-b094-86d1c87e32c6@suse.com> (raw)
In-Reply-To: <20260707142736.2330146-1-neelx@suse.com>



在 2026/7/7 23:57, 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
> 
> It passed all my tests. Hopefully nothing blows. Enjoy testing.

Reviewed-by: Qu Wenruo <wqu@suse.com>

Although I still think some corner cases may change in the future, but 
considering it's already hidden behind experimental, we should have 
plenty time before pushing it to end users.

Will push it to devel after a full selftest.

Thanks,
Qu


> 
> v3:
>   * dropped first patch and improved inline extent length checking
>   * correctly squashed the context key definitions into "btrfs-progs: add
>     inode encryption contexts"
>   * inline extents also show the encryption field now in tree dump
> 
> v2: https://lore.kernel.org/linux-btrfs/20260624165144.556908-1-neelx@suse.com/
>   * works with v7 of the kernel fscrypt series
>   * the on-disk format changed and parts of the series had to be reworked
>     - particularly the encryption context is now stored as dedicated item
>       and not glued onto extent data item
>   * also parses the ENCRYPT inode item flag
> 
> Daniel Vacek (1):
>    btrfs-progs: recognize ENCRYPT inode item flag
> 
> 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: print encryptin type field of file extents
>    btrfs-progs: handle fscrypt context items
>    btrfs-progs: check: update inline extent length checking
> 
>   check/main.c                    | 34 ++++++++++++++++++---------------
>   kernel-shared/ctree.h           |  1 +
>   kernel-shared/print-tree.c      | 28 +++++++++++++++++++++++++--
>   kernel-shared/tree-checker.c    | 17 ++++++++++-------
>   kernel-shared/uapi/btrfs.h      |  1 +
>   kernel-shared/uapi/btrfs_tree.h | 11 +++++++++++
>   libbtrfsutil/btrfs.h            |  1 +
>   7 files changed, 69 insertions(+), 24 deletions(-)
> 


      parent reply	other threads:[~2026-07-08  5:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 14:27 [PATCH v3 0/7] btrfs-progs: fscrypt updates Daniel Vacek
2026-07-07 14:27 ` [PATCH v3 1/7] btrfs-progs: add new FEATURE_INCOMPAT_ENCRYPT flag Daniel Vacek
2026-07-07 14:27 ` [PATCH v3 2/7] btrfs-progs: start tracking extent encryption context info Daniel Vacek
2026-07-07 14:27 ` [PATCH v3 3/7] btrfs-progs: add inode encryption contexts Daniel Vacek
2026-07-07 14:27 ` [PATCH v3 4/7] btrfs-progs: print encryptin type field of file extents Daniel Vacek
2026-07-07 22:40   ` Qu Wenruo
2026-07-08  4:38     ` Daniel Vacek
2026-07-07 14:27 ` [PATCH v3 5/7] btrfs-progs: handle fscrypt context items Daniel Vacek
2026-07-07 14:27 ` [PATCH v3 6/7] btrfs-progs: check: update inline extent length checking Daniel Vacek
2026-07-07 22:43   ` Qu Wenruo
2026-07-08  5:00     ` Daniel Vacek
2026-07-08  5:07       ` Qu Wenruo
2026-07-07 14:27 ` [PATCH v3 7/7] btrfs-progs: recognize ENCRYPT inode item flag Daniel Vacek
2026-07-07 14:33 ` [PATCH v3 0/7] btrfs-progs: fscrypt updates Daniel Vacek
2026-07-08  4:59 ` Qu Wenruo [this message]

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=b7861828-64d1-4fef-b094-86d1c87e32c6@suse.com \
    --to=wqu@suse.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neelx@suse.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