All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
To: linux-btrfs@vger.kernel.org, kernel-team@meta.com
Cc: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: [PATCH 0/8] btrfs-progs: add encryption support
Date: Thu, 29 Jun 2023 15:57:58 -0400	[thread overview]
Message-ID: <cover.1688068420.git.sweettea-kernel@dorminy.me> (raw)

This is the progs side of the encryption feature [1]. The first four
changes are attempts to replicate the relevant kernel changes precisely
to the equivalents in kernel-shared; the next four add support to check
and dump-tree.

[1] https://lore.kernel.org/linux-btrfs/cover.1687988380.git.sweettea-kernel@dorminy.me/T/#t

Sweet Tea Dorminy (8):
  btrfs-progs: add new FEATURE_INCOMPAT_ENCRYPT flag
  btrfs-progs: start tracking extent encryption context info
  btrfs-progs: add inode encryption contexts
  btrfs-progs: save and load fscrypt extent contexts
  btrfs-progs: interpret encrypted file extents.
  btrfs-progs: handle fscrypt context items
  btrfs-progs: escape unprintable characters in names
  btrfs-progs: check: update inline extent length checking

 check/main.c                    | 28 ++++++++-------
 kernel-shared/accessors.h       | 31 ++++++++++++++++
 kernel-shared/ctree.h           |  3 +-
 kernel-shared/fscrypt.h         | 30 ++++++++++++++++
 kernel-shared/print-tree.c      | 64 +++++++++++++++++++++++++++++++--
 kernel-shared/tree-checker.c    | 37 ++++++++++++++-----
 kernel-shared/uapi/btrfs.h      |  1 +
 kernel-shared/uapi/btrfs_tree.h | 16 ++++++++-
 8 files changed, 184 insertions(+), 26 deletions(-)
 create mode 100644 kernel-shared/fscrypt.h


base-commit: a0f1c5308320d781d13f6ecd8c127c6609b32281
-- 
2.40.1


             reply	other threads:[~2023-06-29 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 19:57 Sweet Tea Dorminy [this message]
2023-06-29 19:57 ` [PATCH 1/8] btrfs-progs: add new FEATURE_INCOMPAT_ENCRYPT flag Sweet Tea Dorminy
2023-06-29 19:58 ` [PATCH 2/8] btrfs-progs: start tracking extent encryption context info Sweet Tea Dorminy
2023-06-29 19:58 ` [PATCH 3/8] btrfs-progs: add inode encryption contexts Sweet Tea Dorminy
2023-06-29 19:58 ` [PATCH 4/8] btrfs-progs: save and load fscrypt extent contexts Sweet Tea Dorminy
2023-06-29 19:58 ` [PATCH 5/8] btrfs-progs: interpret encrypted file extents Sweet Tea Dorminy
2023-06-29 19:58 ` [PATCH 6/8] btrfs-progs: handle fscrypt context items Sweet Tea Dorminy
2023-06-29 19:58 ` [PATCH 7/8] btrfs-progs: escape unprintable characters in names Sweet Tea Dorminy
2023-06-29 19:58 ` [PATCH 8/8] btrfs-progs: check: update inline extent length checking Sweet Tea Dorminy

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=cover.1688068420.git.sweettea-kernel@dorminy.me \
    --to=sweettea-kernel@dorminy.me \
    --cc=kernel-team@meta.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.